An Everstack operator controlling connected gateway, agent, sandbox, and observability systems from one command station

EVS agent runtimeearly access

Agents as code. A runtime that's yours.

Define identity, skills, tools, policy, subagents, and schedules beside your code. Run tool-using agents with persistent sessions and isolated sandboxes on infrastructure you control. After a server restart, interrupted turns must be reissued from the last checkpoint; they do not automatically replay.

Start with $5 creditRead agent docs

One-time starter credit per account on Everstack Cloud. Expires 30 days after signup.

  • Open source
  • Persistent sessions
  • Isolated sandboxes
  • Deploy anywhere
Deployments / Agents5 agents
customer-support-botRunning
rag-retrieverWaiting
sentiment-analyzerEphemeral
code-reviewerApproval

customer-support-bot

PersistentRunning@support

Model

gpt-5.2-codex

Tools

5

Max turns

24

Permission

Ask on write

Agent as code

One repository. Six runtime contracts.

EVS keeps the intent human-readable and the execution contract explicit. Every file has a visible effect in the runtime ledger, so a pull request can explain what the agent will become.

instructions.md

Identity and operating boundaries

A reviewable description of the role, constraints, and completion criteria.

agent.yaml

Runtime, model, memory, and policy

One portable manifest for lifecycle, limits, isolation, and approvals.

skills/ + tools/

Focused guidance and typed actions

Load knowledge only when relevant and keep every action schema explicit.

subagents/ + schedules/

Delegation and scheduled background work

Specialized workers and recurring tasks use the same session and policy plane.

Ownership boundary

The framework ends where your infrastructure begins.

Run the same definition on a laptop, in Docker, or across Kubernetes. Everstack carries session state, identity, policy, and telemetry through each target without turning your agent into a vendor-specific deployment.

Develop locally

Inspect files, stream events, and test tool calls without a remote control plane.

Isolate execution

Choose Docker, Firecracker, or Kubernetes based on the trust boundary.

Operate with proof

Keep approvals, traces, usage, and runtime policy attached to every session.

Questions

The short version, before you commit.

These product surfaces are intentionally direct: a small source model, an observable execution path, and infrastructure boundaries you can explain.

Is EVS a library or a hosted service?

EVS is the agent-as-code experience layered over Everstack's open-source runtime. You can run the platform yourself with Docker or Kubernetes and keep execution, state, and telemetry in your environment.

What does Everstack manage for an agent?

The runtime manages sessions, tool dispatch, sandbox provisioning, approvals, memory, subagent coordination, streaming events, limits, and deployment lifecycle.

Can the same agent run locally and in production?

That is the goal of the EVS repository contract: keep the agent definition portable while choosing local, Docker, or Kubernetes execution for each environment.

Can EVS work with existing tools and MCP servers?

Yes. Everstack can expose built-in tools, custom functions, HTTP integrations, and federated MCP tools through the same runtime policy and trace context.