Enterprise
Methods runs where your code is, keeps its records in your repository and leaves the decisions only a person should make with your people.
Deployment
There is no hosted service to adopt. Two ways to run it are planned.
Local
The engine and a background program run on a developer machine, with state in the repository.
PlannedSelf-hosted
The same engine runs on your own infrastructure, so work happens inside your network.
Planned
Governance
- Decisions Methods will not make for you
- Some choices, such as changing the architecture's rules, are never made by Methods. They are raised to a person on your team when they block work, and the answer is recorded.
- Record of every run
- Every run is saved in your repository: what was attempted, by which AI agent, at what cost.
- Record of every verification
- Every verification is tied to the version of the code it checked, with its evidence, so you can see why a change merged.
- Your repository is the record
- Because state is versioned with the code, access control and retention follow the rules you already apply to your repository.
Procurement
Security architecture, a data processing agreement and a questionnaire response are being prepared. The security page lists what exists today and what does not.
Methods is pre-alpha. Enterprise deployment is a design, not a service you can buy today.
Build with us as a design partner.
Methods is pre-alpha. A small number of teams will run it on real work while it is built, and shape what it becomes.