Developer Platform
This section is the main path for developers building with Aionis. It explains what to install, how to run the local Runtime, and which integration path to choose before you read the deeper product pages.
Start with the local Runtime quickstart. From there, connect the surface that matches your host: TypeScript SDK, raw HTTP, MCP bridge, AIFS, native plugins, multi-agent host contracts, or Memory Firewall for external memory backends.
Recommended Path
| Step | Page | Result |
|---|---|---|
| 1 | Quickstart | Run the fastest local loop. |
| 2 | Choose an Integration | Pick SDK, HTTP, MCP, AIFS, native plugin, multi-agent, or Memory Firewall. |
| 3 | Install Aionis | Runtime, SDK, and optional MCP bridge are installed locally. |
| 4 | Run the Runtime | Aionis is listening on loopback with embeddings configured. |
| 5 | First Agent Loop | You complete observe -> guide -> feedback -> measure -> snapshot. |
| 6 | Plugins | Connect SDK, HTTP, MCP, AIFS, native plugins, or external memory. |
| 7 | Runtime Configuration | You know how to run the local-first Runtime cleanly. |
What To Read Next
- Use Execution Memory if Aionis will record and adjudicate task history.
- Use Memory Firewall if you already have Mem0, Zep, a vector DB, markdown notes, or another memory backend.
- Use Using Aionis when you are wiring the Runtime loop into an Agent host.