Skip to content

Trust and security

Your code protected. Your people in control.

Here’s what FlashTeams keeps, who can reach it, and where your people make the call.

01/ Your code

Structure, not contents.

  • Software DNA stores your software’s structure, not your file contents.
  • Reading source code is off by default. An administrator turns it on, and each FlashBrain session still asks before it reads a file.
  • Databases are read for structure, never rows. SQL Server works with a login that can’t select data, and Supabase is read through a read-only endpoint.

02/ Access

Each organization on its own. Each product checked.

  • Each organization’s software DNA lives in its own schema, and your organization always comes from your sign-in, never from the request.
  • Agents, Flash Swarm and Product Center only reach the products a person is allowed to see. Anything else is removed from the answer.
  • Every query against your software DNA is logged.

03/ Credentials

Secrets locked. Keys kept apart.

  • Repository tokens, IBM i passwords and database passwords we hold for you are encrypted, and the key is kept outside the database.
  • Our own services sign in to their cloud and database with keyless workload identity, not stored keys.
  • Forms sent through this website are stored separately from the product database.

04/ AI agents

Agents work inside the limits you set.

  • Flash Swarm runs with spending limits, defined boundaries and points where a person approves.
  • Factory Floor automations have permissions, spending limits and your choice of which agents can act.
  • Engineers review changes before they’re accepted.

Where we stand

Certifications
[Compliance status to be confirmed]
Security contact
[Security contact to be confirmed]

Bring us your security questions.

We’ll walk your team through how FlashTeams handles your code, data and access.