Environments
Ananke Labs provides separate environments for development and production. This page explains how they differ and how to configure your integration for each.
Base URLs
| Environment | Base URL | Purpose |
|---|---|---|
| Production | https://api.anankelabs.net/v1 | Live data, real anchoring, production quotas |
| Local development | http://localhost:5300/v1 | Full local stack — all services, no external dependencies |
Environment differences
| Feature | Production | Local |
|---|---|---|
| Anchoring | Real chain anchoring (Hedera Hashgraph) | Simulated / local anchoring |
| API keys | Issued from Console, full entitlement checks | Seeded via local scripts |
| Rate limits | Plan-based limits apply | No limits enforced |
| Data | Persistent, backed up | Ephemeral — resets when infra restarts |
| Email delivery | Real delivery via configured provider | Captured locally (no real delivery) |
Local development
The recommended local setup runs all backend services and infrastructure via Docker Compose and the Ananke Labs dev scripts. This gives you a complete local replica of the platform.
Prerequisites:
- Docker Desktop with Compose v2
- .NET 9 SDK
- Node.js 18+
Start infrastructure (PostgreSQL, Redis, MinIO, Vault) first, then the .NET services. The Integration API will be available on http://localhost:5300.
Data persistence
In production, all data is persisted to PostgreSQL with regular backups. Anchoring receipts are written to the chain and cannot be undone.
In local development, PostgreSQL data is stored in a Docker volume. Restarting Docker preserves data, but running docker compose down -v removes all volumes. There is no anchoring in local mode.