What was asked
Each agent session saves what it was asked to do as a spec change. It lands on its own branch for a person to merge.
Ship with proof
The audit trail for AI-generated code.
What each change was for, what checked it, and who signed off.
- Specs verified14 of 14
- Checks run212 · 0 failing
- Risk accepted1 · with a reason
- Production issues0 open
- Password reset link expires after 30 minutes3 checks · pass
- Sessions end when the password changes5 checks · pass
- Account export includes archived usersrisk accepted · reason on file
Snapshot locked at release · 14:02 UTC
Every change leaves a record
Whether it shipped
Hard failures block the release. Risk is accepted only with a reason on file.
What broke after
Each production error links to its release and the specs it touches.
Who did what
Every event shows who did it: a person, an agent, the API, or the system. Stream it to your SIEM.
Where your code goes
Your systems
- RepositoriesOnly the ones you pick, via GitHub or GitLab
- CI test resultsFrom the reporters you add
- Jira, Linear, NotionIf you connect them
- Production errorsIf you send them
Tiden
- Specs and verdictsVersioned and merged like code
- Release snapshotsLocked when created
- Activity logStreams to your SIEM
- Your code, by referencePaths, lines, SHAs, short excerpts
- CredentialsEncrypted, each under its own key
Models
- Your LLM keysFor agents you configure
- Anthropic or OpenAITo draft and search specs, on Tiden’s account
Who can do what
Sign in with SAML through your identity provider. Require two-factor or passkeys for everyone. SCIM keeps members in sync, and roles set who can change what.
- SAML single sign-onSign in through your identity providerOn
- SCIM 2.0 provisioningUsers and groups sync from your IdPOn
- Two-factor or passkeysRequired for every memberRequired
- RolesOwner · Admin · Member, per organization and workspace3 roles
Security and compliance
Held by Qase, Inc. Ask for the reports.
- ISO/IEC 27001Information security
- SOC 2 Type IIControls audited over time
- SOC 3Public summary of SOC 2
FAQ
Still have one? Write to us.
Which models see our code?
Tiden uses Anthropic or OpenAI, on its own account, to draft your specs and to search them. Agents you configure in Tiden can run on your own LLM keys.
What does Tiden keep from our code?
File paths, line ranges, commit SHAs, and short excerpts, so each spec can point to the code it describes.
What access does Tiden need to our repositories?
Only the repositories you pick, through the Tiden GitHub App or a GitLab authorization. You can remove access at any time.
Can we get the audit trail into our SIEM?
Yes. Organization admins stream the activity log over HTTPS or to Splunk, as it happens.
How do we evaluate Tiden?
Start a 14-day Team trial on one product, with your own repositories and agents. Talk to us when you’re ready to roll out.
How is Enterprise priced?
By the number of products and verified changes. Developers and agents are unlimited.
Bring your security questionnaire.
We’ll work through it with you before you sign.