Before we start
How do we start?
Send a short brief with what you want built or tested. We reply with questions, then a scope and a quote.
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.
Do you sign an NDA?
Yes. Send yours, or ask for ours, before sharing anything sensitive.
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.
Testing
Will testing take my site down?
Testing is planned to avoid disruption. Anything that could affect availability is agreed with you first, or run against a staging copy.
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.
Do you test mobile apps?
We test web applications and the APIs behind them, including the APIs your mobile app talks to.
Is a retest included?
Yes. One retest of the reported findings is part of every test.
Building
Who owns the code?
You do. The repository, the infrastructure accounts and the documentation are handed over to you.
Which stack do you build on?
Laravel and PHP or Node.js on the back end, React or Vue on the front end, Python for tooling and automation. If your project already has a stack, we work in it.
Do you maintain the site after launch?
Yes, on request, as a separate maintenance agreement.
Got something to build, or something to break?
Tell us what it is. A few lines are enough to start.