Secure your FlutterFlow application

From your application to the next action

• Website and API after ownership proof and authorization
• Code through the GitHub App, on selected repositories
• Connected databases read-only, with your approval
• Prioritized findings, evidence and next action

Getting started with FlutterFlow

1. Add the exact address of your deployed website, regardless of the tool used to build it.
2. Prove that domain at its hosting provider: add the requested DNS TXT record, or publish the text file at /.well-known/hackaiz-verification.txt. For a framework using public, the source path is public/.well-known/hackaiz-verification.txt. A code editor or database is not necessarily your website host.
3. To inspect code, export or sync your project to a GitHub repository if your tool supports it, then select that repository in the Hackaiz GitHub App. For a Supabase database, use its separate read-only connection.
4. Start the analysis, review the evidence and approve each desired fix individually.

An evidence-based check

Checks are non-destructive. The report states what was checked, the results and any missing access. You retain control over permissions and changes.