Agent deployments

Package agents as production deployments.

Turn agent code into versioned, reproducible deployments with runtime metadata, tools, skills, knowledge, policies, and environment requirements.

deployment manifest
agent: claims-assistant
version: 1.2.0
runtime: python
entrypoint: claims:agent
tools:
  - lookup_policy
  - create_case
skills:
  - claims-playbook
  - escalation-guide
knowledge:
  - policy-docs
  - customer-graph
environment:
  runner: private-cloud
policy: production

Agent code is not a production boundary.

Production agents need more than source code and prompts. They need a deployable contract that defines how they run, which tools they can use, which skills and knowledge they can access, where they execute, and which policies apply.

Agent code
Deployment contract
Versioned runtime
Controlled execution

Everything the runtime needs to execute an agent safely.

A sypho deployment describes the operational shape of an agent. It connects code, runtime, tools, skills, knowledge, policies, and target environments into one versioned unit.

Deployment includes
Agent version
Runtime and entrypoint
Tool definitions
Skills
Knowledge scope
Environment variables
Secrets references
Runner target
Runtime policies
Promotion state

From local package to promoted production version.

Build
Package
Preview
Validate
Promote
Run
Observe

sypho gives agent teams a repeatable deployment path. Package once, validate in preview, promote intentionally, and observe every run after release.

Package

Create a reproducible deployment with manifest, runtime, tools, skills, knowledge, and policy metadata.

Preview

Run scenario tests against a new version before production traffic reaches it.

Promote

Move validated versions into production while preserving traceability and rollback paths.

Safer agent changes before production traffic.

Agent behavior can change when prompts, tools, skills, knowledge, models, or environments change. Deployments give teams a place to validate those changes before users or customers depend on them.

Pull request
Preview deployment
Scenario runs
Trace review
Promotion
Production deployment
compare versions before promotion
validate tool and skill access
test knowledge scope
inspect traces
reduce release risk

Why teams deploy agents through sypho.

Reproducible releases

Package runtime configuration with the agent version, not scattered across scripts and environments.

Environment-aware execution

Target local, private cloud, customer cloud, on-prem, hybrid, or managed runners.

Controlled access

Attach tools, skills, knowledge, secrets, and policies intentionally per deployment.

Safer promotion

Preview, validate, promote, and roll back agent versions with clearer operational discipline.

Full traceability

Connect every production run back to the deployment version and runtime configuration that produced it.

Deploy agents with production discipline.

Join the sypho waitlist and help shape the runtime layer for agentic software.

Join waitlist