Use cases

Arqen is useful whenever a backend needs explicit operations, durable data, background work, or clear runtime checks.

Product backends

Build APIs for web or mobile products with authentication, validation, domain modules, storage adapters, health endpoints, and OpenAPI helpers.

Start with: Build a backend and Getting started.

Agent-enabled operations

Expose selected application operations as typed tools. Describe inputs, outputs, required scopes, read/write effects, and retry behavior in the agent manifest. The same backend can continue serving normal HTTP clients.

Start with: Typed tools and Agent guide.

Long-running automation

Move email, indexing, imports, synchronization, and enrichment out of request handlers. Thingd queues provide leases, retries, idempotency metadata, and dead-letter states for workers.

Start with: Durable jobs.

Local-first development

Use memory mode for fast tests and prototypes, then switch to native Thingd or an HTTP Thingd service without changing domain repository interfaces.

Start with: Configuration and Thingd integration.

Human and machine operations

Use one HTTP service from dashboards, scripts, CI, applications, and agents. Health, readiness, structured logs, and metrics make it easier to understand whether the service and its dependencies are working.

Start with: Health, Observability, and Production runbook.