Gravity Network
The layered infrastructure powering Agentuity's services
The Gravity Network is Agentuity's infrastructure layer that powers all platform services. Rather than building monolithic, tightly-coupled systems, we've architected everything as composable primitives that stack on top of each other.
Layered Architecture
Agentuity is built on a layered primitive model. Each layer provides building blocks for the layers above it, creating a flexible and powerful foundation.
Core Primitives
At the foundation, we have core primitives that nearly everything else is built upon:
| Primitive | Purpose | Examples |
|---|---|---|
| Storage | S3-compatible object storage | File uploads, snapshots, assets |
| Postgres | Transactional database | Metadata, state, configuration |
| Compute | Agent runtime and sandboxes | Agent execution, isolated code runs |
| OLAP Warehouse (coming soon) | Analytical database | Logs, metrics, analytics |
These core primitives are intentionally generic and protocol-based. Storage speaks S3. Databases speak standard wire protocols. This design enables portability and flexibility at the infrastructure level.
Platform Primitives
On top of the core primitives, we build higher-level platform primitives:
| Primitive | Built On | Purpose |
|---|---|---|
| Database | Postgres | Managed database access |
| Key Value | Postgres | Fast state storage |
| Vector | Postgres | Semantic search |
| Queue | Postgres | Reliable message delivery |
| Sandbox | Compute + Storage | Isolated code execution |
| Durable Stream | Storage | Persistent message streams |
| Agent Runtime | Compute | Agent execution environment |
| Observability | Warehouse | Logging, tracing, metrics |
These primitives use the Core Primitives but don't depend on each other horizontally. They only reach down the stack, never up.
Application Services
The highest layer provides application-level services that combine multiple Platform Primitives:
| Service | Built On | Purpose |
|---|---|---|
| Auth | Database | User authentication and sessions |
| Webhooks (coming soon) | Queues + Compute | Receive external events |
| Scheduling (coming soon) | Queues + Compute | Cron and delayed execution |
| Email (coming soon) | Webhooks + Queues | Inbound/outbound email handling |
| App Analytics | OLAP Warehouse | Metrics, dashboards, insights |
For example, an inbound email service works like this:
- Email arrives at the Agentuity email service
- The email is processed by a preconfigured webhook
- An event is placed on the queue
- This triggers the Agent Runtime where you can process the email
- Store the email in Storage for long-term retention
Each service is composed from lower-level primitives rather than built from scratch.
Why This Matters
Composability: Higher-level services are built from lower-level primitives. Need a new capability? Combine existing primitives rather than building from scratch.
Portability: Because Core Primitives use standard protocols, the underlying infrastructure can be swapped. Your workloads aren't locked into proprietary systems.
Reliability: Built on battle-tested primitives like Postgres and S3, not experimental infrastructure. Your agents run on foundations that have proven themselves at scale.
Agentic: Since you can peek behind the curtain and see what's happening across these abstractions, your agents can too. This creates better context and feedback loops, allowing your agents to build software quickly and effectively.
Need Help?
Join our Community for assistance or just to hang with other humans building agents.
Send us an email at hi@agentuity.com if you'd like to get in touch.
Please Follow us on
If you haven't already, please Signup for your free account now and start building your first agent!