Security and governance
Built to be trusted with your code and your customers
Maestro touches your repositories, your agents and your users' requests. So isolation, short-lived access, encryption and a clear record are part of its design, not add-ons.
Tenants kept apart
Row-level security
Every tenant-scoped table carries the tenant, and the database itself enforces that a tenant sees only its own projects, agents, runs and keys.
No shortcuts
The application connects with a database role that cannot bypass those rules, and Maestro's health check fails if it could.
Roles from membership
A person's role (owner, operator or member) is read from their membership, never from the request.
No standing credentials
Short-lived GitHub access
GitHub is reached through a GitHub App installed per repository. Access tokens are created for each call.
Keys encrypted per tenant
Vendor and runtime keys are encrypted at rest under a key derived for your tenant alone, written through write-only screens, and shown only as 'set on' a date.
Secrets never shown
After it is set, a secret never appears in an answer, a log, an audit row, a pull request or a commit. Issued keys and tokens are shown once, at issue.
Short, single-use hand-over
A product signs a user over to the console with a token that lasts two minutes and works once.
Key rotation
Rotate a project's keys with an overlap period, so the old key keeps working while the new one rolls out.
Your repository, your rules
Pull requests, not pushes
Every file Maestro adds to a repository arrives as a pull request. A run never pushes to a protected branch.
Branch protection required
Maestro requires branch protection on the default branch before it runs, and checks your branch model.
Allowlisted names
Every secret, variable and onboarding file Maestro writes to GitHub is checked against a fixed allowlist of names.
Checked text only
A run receives the issue's checked text. It never receives the user's attachments.
On the record
Versions and links
Every agent version is recorded: the hash of its instructions and documents, who published it and when. Every development run is linked to its issue, pull request and release.
Logs without content
Logs carry names, ids, counts and hashes. Never a prompt, a document, a person's words or a key.
Audited actions
Agent publishes, key changes, onboarding steps and run decisions are audited, with who did them.
In your control
People at the gates
Agents propose. People submit specifications, approve development, approve articles and promote releases.
Every part switchable
Each part has its own switch and is simply not there when off. Use agents alone, runs alone, or all of it.
Sign-in by e-mailed code
Console accounts sign in with a one-time code sent by e-mail. Sessions expire.
Privacy built in
Personal data in messages, specifications and reports is redacted by rules that cannot be switched off. Documents that cannot be checked are refused.
Bring your product team into the loop
Maestro is ready to deploy on your product. Tell us about your product and your team, and we will show you how Maestro runs it.
Your product's AI team and delivery pipeline, with people at every gate.
Maestro is part of the TALOS MaiND family.