Workspace
Run agents and continue work
Chat, launchers, recent runs, resumable sessions, and memory-backed runtime work live in one place.
Product
One enterprise platform to run agents, govern models, and control runtime actions.
Atellagent gives enterprise teams a hosted platform for building and running agents and workflows plus vendor-neutral control across external runtimes. Manage identity, model access, runtime policy, and attributable evidence from one control surface.
Start with governed visibility, then tighten policy into enforcement over time.
Core Platform
The main surfaces teams use to operate governed agent systems.
Dashboard
Track operations and review signals
Queue health, review backlog, and change signals stay connected to the runtime activity they describe.
Workflows
Design, deploy, and operate automations in a visual workflow builder
Build workflow logic, configure hosted agents inside workflow deployments, manage executions, and resume governed sessions from one runtime system.
Policies
Define controls and review decisions
Teams can author policy, manage roles and data, and review decisions against the evidence attached to them.
Visibility
Inspect decisions, side effects, and replayable evidence
Replay, telemetry, audit events, side effects, and investigations stay connected to the execution activity they describe.
Organization
Manage identities, ownership, and provider access
Manage users, roles, enterprise SSO, service accounts, provider access, and inventory for connected agents, MCP servers, channel adapters, and deployment identities from one control surface.
Deployment And Integration
Adopt Atellagent as the hosted runtime for configured agents and workflows, connect external runtimes, or run both together.
Adopt the managed runtime, connect existing runtimes, or run both together without changing the control model.
Hosted Runtime
Run first-class agents and workflows directly in Atellagent
Use Atellagent as the managed runtime when you want the strongest built-in control posture.
Bridge Participation
Keep an external runtime in place while Atellagent governs the control contract
Connect customer-owned execution without rebuilding policy and evidence around a separate stack.
SDK Participation
Embed governed outbound calls directly into an existing process
Keep runtime ownership where it is while standardizing how governed calls leave the process.
Models And Detectors
Bring your own models and detectors under the same runtime policy.
Atellagent treats models and detector-driven controls as governed participants, not bolt-ons.
Custom Models
Use built-in provider integrations or add custom model endpoints
Bring your own models into the platform without rewriting the control path around each provider.
Model Access
Control model access with policy rather than one-off application logic
Keep model governance aligned with identity, workflow state, and runtime context.
Detector-Driven Controls
Use detectors for prompt risk, response release, and organization-specific protections
Bring your own detector models or classifiers for IP, trade-secret, and other enterprise-specific controls.
Architecture Diagram
Hosted and external runtimes stay inside the same governed path.
Hosted and external runtimes pass through the same secure runtime mesh, where identity, policy, and evidence stay attached before actions reach downstream systems.
Rollout Path
Start with visibility, then tighten into enforcement.
Some teams start with coding agents, then expand the same control model into broader enterprise workflows.
Land
Bring identity, runtime evidence, and policy evaluation online
Start with governed visibility instead of day-one hard blocking.
Observe And Tune
Run decisions in advisory mode and refine policy against real workloads
Tighten by action class and risk surface as evidence accumulates.
Enforce And Expand
Turn on blocking gradually, then extend the model to broader workflows
Choose a starting workflow, then expand the same control model across automations and other enterprise agent systems.
Walk through the platform, then go deeper on the runtime boundary.
A product demo covers the hosted platform and adoption path. The Architecture page explains the deeper runtime model behind it.