Know where the work runs and who owns each boundary.

Jentra coordinates work. The selected runtime, model, repository and delivery providers still own execution. This page makes cost, security and operational responsibility explicit before you connect them.

No hidden transfer of responsibility

Changing deployment mode never silently expands an agent's authority or moves reusable secrets into Jentra.

Deployment modes

Charges depend on the services you connect and the work agents perform. Jentra shows the selected runtime's cost class when it is advertised, but your provider invoices remain the source of truth.

Hosted experimentjentra.dev

Jentra operates: Authentication, coordination state, hosted limits, product updates and the public control plane.
You operate and pay: Your model, agent, repository, runtime and external tool accounts, including usage they incur.
Recovery boundary: Jentra preserves canonical work and evidence. Connected providers remain responsible for their execution availability.

Local self-hostingYour machine or private server

Jentra provides: A signed experimental release, integrity materials and setup documentation.
You operate and pay: Compute, storage, networking, backups, updates, model accounts, secret stores and connected tools.
Recovery boundary: You restore the deployment and its data. Jentra's portable contracts help runtimes continue from recorded context.

User-owned CloudflareYour Cloudflare account

Jentra provides: Deployment configuration and compatible coordination contracts.
You operate and pay: Your Cloudflare usage, Workers AI or external models, storage, email, domains and runtime execution.
Recovery boundary: You control account policy, billing, secrets, observability and rollback. Cloudflare's service terms also apply.

External runtime hostIDE, CLI, harness or another cloud

Jentra coordinates: Eligibility, dispatch, alignment, cancellation, checkpoints, evidence and explicit authority boundaries.
The runtime operator owns: Isolation, tools, models, credentials, provider charges, process recovery and truthful capability advertising.
Evidence returned: Bounded checkpoints, results and content-addressed tool-effect receipts rather than reusable credential values.

Rules that do not change

These boundaries apply whether work runs beside you or on an online provider.

Secrets stay with an approved secret system. Jentra coordinates opaque, revocable references.
Capability matching fails closed. A runtime that lacks required tools, versions or authority is not eligible.
Consequential effects remain attributable. Publish, send, spend, delete and deployment actions require the configured policy and return receipts.
Verification is not delivery. A verified result does not automatically merge, publish, deploy or spend.
Provider terms still apply. Jentra cannot replace the security, acceptable-use, billing or availability terms of services you connect.

Before dispatching work, inspect the runtime directory to see current eligibility, capacity and advertised cost responsibility. Use the guide to configure local or user-owned execution.

Inspect runtimes