Features & security
Everything a governed agent fleet needs.
From the idea to the merge — planning, isolated execution, automated review, human approval, and the operational controls an enterprise platform team asks for. Themis is in private beta, and design partners shape what lands first.
Items marked Next are on the roadmap, not shipped.
Capabilities
The product, group by group.
Plan & decompose
- Spec drafting a functional spec and use cases from a plain-language description
- Automatic task breakdown with sizes, priorities and dependencies
- Collision-aware planning the planner sequences same-file work so parallel tasks don't conflict
- Task templates with preset parameters, so the least experienced developer files the same quality task as your best
- Plan approval gate nothing runs until a lead signs off
- Single-task mode for exploratory, prompt-after-prompt work
Run & orchestrate
- One isolated git workspace per task cloned from your repository and wiped on demand
- Cross-repository delivery frontend, backend and shared libraries land as one reviewable unit
- Parallel agents with hard run timeouts
- Model choice at promotion so you decide which deployment each task uses
- Continuous auto-start of ready tasks, opt-in per board
Review & ship
- Review agents on every push QA, security checks and third-party integrations run before a person looks
- Accept, edit or revert each individual change
- Edit the code yourself before the merge
- One-click full-stack environments frontend and backend wired together behind a live URL
- Full transcripts and logs agent reasoning, run events and container output in one place
- Bulk board operations multi-select promote, move and delete
Connect
- Any git remote GitHub Enterprise Server, GitLab Self-Managed, Bitbucket Data Center, or cloud GitHub, GitLab and Bitbucket
- Trackers The built-in board and Linear Next Jira, Azure DevOps
- Models Azure OpenAI and Azure AI Foundry Next AWS Bedrock
- Agent runtimes Claude Code, Codex, or an HTTP model backend, through one adapter
- Environment files injected at runtime and never committed
Govern & measure
- Auth on every surface web UI and API
- Scoped API keys per user, per workspace and per team
- Branch allowlists per repository
- Admin view across the whole team and every workspace
- Usage and outcome statistics tokens, cost, tasks merged and review outcomes by user, workspace and model
Deploy
- Fully managed SaaS for teams without a private-cloud mandate
- Private cloud deployed on your own VM or cloud account
- AWS and Azure Marketplace listings bought against committed spend Next
- A 90-day paid pilot on one team, credited in full to year one
Security
The security model is the product.
Themis was not built as a cloud service with an on-premise option bolted on. It starts from the constraint a regulated engineering estate actually has: nothing leaves the boundary, and no machine merges code on its own.
Nothing leaves your network
Your code, prompts and diffs stay inside your own boundary. Inference goes to the model deployment you already own (Azure OpenAI or Azure AI Foundry today, AWS Bedrock next) under your IAM, in your account and region. There is no call home, and no telemetry that carries source.
Isolation per task, not per tenant
Every task runs in its own throwaway git workspace cloned from your repository, wiped after merge. Hard run timeouts bound each run; branch allowlists bound its reach. Parallel agents cannot see one another's workspaces.
A human owns every merge
Agents propose; people decide. Accept, edit or revert each individual change, and edit the code before it lands. Auto-approve exists, but it's a person's opt-in per task and off by default. Review agents advise the reviewer — they never hold the gate themselves.
Auditable by construction
Every run, prompt, tool call, review decision and merge is recorded: agent transcripts, run events, per-user and per-workspace statistics, and an admin view across the team. Built so a vendor-security questionnaire can be answered from the record, not reconstructed afterwards.
What Themis never does
- ✕Train on your code, prompts or diffs
- ✕Route inference through our infrastructure
- ✕Store your source outside your network
- ✕Hold vendor API keys on your behalf
- ✕Merge anything without a human approving it
- ✕Require inbound access from the public internet
Because inference runs on your own deployment, model data handling is governed by the cloud agreement you already signed — not by a new one with us. That also keeps your ICT third-party footprint small under DORA: one vendor, with no access to your data plane. SOC 2 Type I is planned, and our isolation and audit documentation is available for security review today.
Private beta
We are onboarding a small number of design partners.
If you run an engineering estate where AI has to stay inside the network — financial services, pharma, defence, insurance, or any Fortune 500 platform team — we would like to talk.
Or email us directly at beta@getthemis.ai