We build websites. Then we try to break them.

Flint designs and ships web products, then tests them the way an attacker would. You get working software and a clear list of what to fix.

  • PHP
  • Laravel
  • JavaScript
  • TypeScript
  • React
  • Vue
  • Python
  • Node.js
  • PostgreSQL
  • MySQL
  • Redis
  • Docker
  • Linux
  • Nginx
  • REST APIs
  • OWASP ASVS

One team for both sides of the job.

Most sites are built by one company and tested by another, months later. We do both, so problems are found while they are still cheap to fix.

Web development

Websites, web apps and APIs, built to be fast, maintainable and safe by default.

  • Marketing sites and landing pages
  • Web apps and dashboards
  • REST APIs and integrations
Details

Penetration testing

Manual testing of your web app and API by people who write this kind of software themselves.

  • Authentication and access control
  • Injection and input handling
  • Business logic and API abuse
Details

Code review and hardening

We read the code, fix what we find with your team, and retest until it holds.

  • Secure code review
  • Fixes and retesting
  • Headers, sessions and server config
Details

Authorise the record, not just the route.

Every controller checks that this user may see this record. Changing an ID in the URL gets a 403, not someone else's invoice.

RemovesBroken access control

$ cat app/Http/Controllers/InvoiceController.php

// authorise the record, not just the route
public function show(Request $request, Invoice $invoice)
{
    $this->authorize('view', $invoice);

    return new InvoiceResource(
        $invoice->load('lines')
    );
}

User input is text, never markup.

Comments, names and profile fields render as text. Raw HTML rendering stays out of the codebase.

RemovesStored cross-site scripting

$ cat src/components/Comment.tsx

// user input is rendered as text, never as HTML
type Props = { body: string };

export function Comment({ body }: Props) {
  return <p className="comment">{body}</p>;
}

// no dangerouslySetInnerHTML anywhere in the codebase

Every finding comes with proof.

What is wrong, where it is, how we showed it, and what it would cost you if someone else found it first.

$ flint report --finding F-01

F-01  HIGH  Session cookie readable from JavaScript

where   POST /login, Set-Cookie header
proof   document.cookie returns the session value
impact  any script injection becomes account takeover
status  open

And the change that closes it.

Not advice. A diff your developers can merge, then the same attack run again to confirm it is closed.

$ flint retest F-01

+ 'http_only' => true,
+ 'secure'    => true,
+ 'same_site' => 'lax',

[ok]  document.cookie no longer returns the session

F-01  fixed, retested
1 finding, 0 open

The stack we build on, and break.

We test what we ship with, so every fix is written in your codebase's own terms.

  • PHP
  • JavaScript
  • TypeScript
  • Python
  • SQL
  • Laravel
  • React
  • Vue
  • Node.js
  • PostgreSQL
  • MySQL
  • Redis
  • Docker
  • Linux
  • Nginx
  • CI/CD
  • Web app penetration testing
  • API security testing
  • Authentication and access control
  • API reverse engineering
  • Secure code review
  • OWASP Top 10 and ASVS

How we work, in four rules.

These hold on every project, whatever the size.

01

Permission first

We only test systems you own or are authorised to test, and only inside a written scope.

02

A fix with every finding

A problem without a fix is half a report. Each issue comes with the change that closes it.

03

Code you can read

You own the repository. It is documented, tested, and written so your next developer can take over.

04

Plain language

Reports are written for the people who have to decide and the people who have to ship. No padding.

See the full process

Questions we get before a project starts.

All questions

Can you test a site you did not build?

Yes. Testing and code review are available on their own. We need written authorisation from the owner and an agreed scope before any testing starts.

Where are you based, and do you work remotely?

Flint is based in Gaza, Palestine. We work remotely with clients across the region and worldwide, in English and Arabic, and plan calls around your time zone.

What do I get at the end of a test?

A report with every finding ranked by severity, the evidence for it, its impact, and a specific fix. After you apply the fixes we retest and update the report.

Got something to build, or something to break?

Tell us what it is. A few lines are enough to start.