Local Runtime Configuration
Aionis ships with a local-first Runtime that is easy to run beside coding agents, custom Agent loops, MCP clients, and SDK integrations.
Included In The Local Runtime
| Capability | Status |
|---|---|
| Local Runtime APIs | Available |
| SQLite-backed local store | Available |
| TypeScript SDK | Available |
| MCP bridge | Available |
| Execution Memory | Available |
| Memory Firewall for external candidates | Available |
| Flight Recorder reports | Available |
Deployment Responsibilities
| Surface | Recommended owner |
|---|---|
| Loopback development | Aionis local Runtime |
| Remote exposure | Host gateway or deployment platform |
| API key / JWT auth | Managed-server configuration |
| Tenant quotas | Host or managed-server deployment layer |
| Secrets and provider keys | Host environment and secret manager |
| Enterprise rollout | Self-managed deployment automation |
Why This Matters
Aionis governs memory and context. Your deployment layer owns network exposure, auth, secrets, and production operations. That split keeps the local install simple while leaving a clear path for self-managed deployments.