Agent types: Cloud and Secure

The Deployment section in the agent editor uses the same labels as this page: Cloud and Secure.

Overview

An agent is always the same Python package. What changes is where the worker runs that package: on Viksa-managed infrastructure (Cloud) or on Chrona workers you operate (Secure).

Cloud

Managed runtime on the platform — what you see in the UI as "Cloud" with the subtitle "Managed runtime on the platform".

No customer-side worker required for the default path
Build and deploy from the app; scaling and patching are platform concerns
Great for public APIs, SaaS tools, and fast iteration
Subject to org and plan limits where applicable
Best for

Integrations that do not need access to your private network or on-prem only systems.

Secure

Run on your Chrona workers — the editor shows this as "Run on your Chrona workers" with the shield affordance.

Data plane stays in infrastructure you connect and trust
Access VPCs, internal HTTP, databases, and on-prem services
You select queues / mapping so jobs land on the right pool
You manage capacity; plan worker limits do not apply the same way as shared cloud pools
Best for

Regulated data, private networks, and any case where exit traffic must stay under your control.

At a glance

FeatureCloudSecure
Runtime managed by ViksaAI (default path)
Runs on infrastructure you connect (Chrona)
Private / on-prem network access
Fastest time-to-first run for internet APIsvaries
Can publish or install from Marketplace

Chrona for Secure agents

To run a Secure agent you install and connect workers so task queues and secrets resolve in your environment. High-level options and the V-Series table live on the Chrona Workers page. Below is a typical Docker bootstrap — replace keys and org identifiers with the values your admin provides.

Example: worker container
docker run -d \
  --name chrona-worker \
  -e VIKSAAI_API_KEY=your-api-key \
  -e VIKSAAI_ORG_ID=your-org-id \
  -v /var/run/docker.sock:/var/run/docker.sock \
  viksaai/chrona-worker:latest