You write the spec. The runtime runs it.
A Kodeus agent is a kodeus.yaml file plus the skills you author. The SDK turns it into artifacts in your own database, and the runtime runs it on your infrastructure. You own the data and the infrastructure.
Kodeus SDK
Validates kodeus.yaml, scaffolds skills and prompts, launches the runtime locally.
Synthesis service
Turns the spec into prompts and artifacts. Operated by Kodeus. Never in the serve path.
Specs, artifacts, memory, traces
Postgres you already run. Everything the runtime needs to serve lives here.
Kodeus runtime
Runs the agent per user with identity, policy, memory and traces. Laptop, VPC, or airgapped.
One file you can read
Model, tools, skills, memory, policy and limits, in one file. Policy is declared, not buried in a prompt.
The same runtime on your laptop and in production
Run it locally with the same policy engine as production. When you deploy from the Console, nothing about the agent changes. Only where it runs.
A correct run is a test
Record a correct run. Replay it after a prompt edit or a model bump. Same path, ship it. Different path, you found the drift before your users did.
Questions developers ask
{{ f.a }}
