A Rust toolkit for HTTP services with explicit modules, durable jobs, health checks, and Thingd storage.
Early-stage project
Arqen is Rust-first and actively maturing. Before production use, validate durability, Thingd compatibility, security, and operational behavior for your application. See Feature status for current readiness.
one service, many workflows
Arqen gives people, programs, and agents the same dependable surface: discoverable capabilities, explicit policies, durable work, and visible health.
Arqen gives your application one place for HTTP routes, authentication, typed tools, durable jobs, health, and storage adapters. Agent tools are optional; the same foundation works for conventional web, mobile, internal, and automation backends.
| You need | Start here | What you get |
|---|---|---|
| A complete backend path | Build a backend | One guided route from project creation to production |
| A quick local prototype | Getting started | A runnable app with memory storage |
| A configurable starter app | CLI generator | Interactive or scripted setup for HTTP, Thingd, examples, and tooling |
| Durable single-process storage | Deployment | Embedded native Thingd with recovery responsibilities clearly stated |
| A separate data service | Thingd integration | The public HTTP adapter and its compatibility requirements |
| To move existing data | Migration | A checked, resumable native-to-HTTP JSONL workflow |
| A Thingd data contract | Thingd schema | Store, validate, inspect, and operate a .thingd schema |
| Agent-facing capabilities | Agent guide | Discovery, permissions, typed inputs, and invocation |
| Production readiness | Production runbook | Deployment checks, health, logs, backups, and ownership |
| Request diagnosis | Logging and Observability | Structured logs, correlation, bounded metrics, and collector handoff |
Follow Build a backend for the complete path: create a project, add a module, add routes/tools/jobs, choose storage, define a Thingd schema, validate it, and prepare a deployment.
cargo run -p arqen --features cli --bin arqen -- new hello-api --yes
cd hello-api
cargo runFor interactive setup, remove --yes. The generator can add native Thingd, starter guidance, and optional Nice Code CI while keeping Nice Code outside the application's Rust and runtime dependencies. Read the CLI project generator guide for the full option set.
Or run the workspace server directly:
cargo run -p arqen --features cli --bin arqen -- dev --storage memory
curl http://127.0.0.1:8888/healthclient or agent → Arqen API → typed tools / policies / jobs / logs
↓
memory · native durable thingd · HTTP sidecar · future cloudApplication code owns domain behavior. Arqen provides HTTP, module, job, health, and adapter integrations. Thingd provides durable data primitives. See Architecture and Thingd integration.
thingd supplies the object, event, search, link, and queue records that Arqen adapts. Arqen keeps that integration optional and public-contract based. Cloud hosting is a future path rather than a current promise.
Learn more about the thingd ecosystem at thingd.cloud, the home for thingd’s hosted data engine and related services.
Typed tools and manifests are optional. Add them when people, programs, or agents need to discover and invoke selected application operations. Read Typed tools and Agent guide.
Read the roadmap for planned work and the Feature status page for what is currently available.
Read the performance guide for benchmarks, profiling, and optimization patterns.