Run Agents Without Infrastructure

Animus is self-contained โ€” it runs on a Raspberry Pi or a laptop with no cloud required. But not everyone wants to manage hardware, open ports, or configure TLS certificates.

Premium services handle the infrastructure layer so you can focus on what your agent does, not where it runs. Three tiers, each independent. Use one or all three.

๐Ÿ”—

Cloud Relay

Mesh nodes connecting disparate networks. Agents behind NAT firewalls reach each other through our relay infrastructure.

What it provides

โ–ธOutbound-only connectivity (no open ports required)
โ–ธEncrypted message routing between mesh members
โ–ธNAT traversal for home/office/cloud deployments
โ–ธMulti-agent coordination across networks

Who it's for

Teams running agents on separate networks who need them to coordinate โ€” home + office, multi-site, or multi-team setups.

๐Ÿ’พ

Cloud Storage

Secure storage for your agent's entire construct โ€” memory, identity, diary, ontology, sessions. Syndicated to a node in our network.

What it provides

โ–ธEncrypted construct snapshots (we can't read your data)
โ–ธScheduled and event-driven syndication
โ–ธDisaster recovery โ€” restore to fresh hardware
โ–ธMulti-device sync โ€” same construct, multiple instances

Who it's for

Anyone whose agent has accumulated months of memory and identity that can't be replaced. Insurance for your agent's continuity.

โ˜๏ธ

Cloud Hosting

We run your Animus agent. You pick channels and an LLM. Your personal AI is talking to you in under 5 minutes.

What it provides

โ–ธManaged Animus instance (always on, always connected)
โ–ธChannel setup via web UI (WhatsApp, Telegram, Signal, etc.)
โ–ธOptional managed LLM (Cohere, Mistral, or Zhipu)
โ–ธAutomatic updates and maintenance

Who it's for

Non-technical users who want a personal AI assistant on their messaging apps. No terminal, no config, no hosting.

Cloud Hosting โ€” The 5-Minute Agent

The goal: a personal AI talking to you on WhatsApp (or Telegram, or Signal) in under 5 minutes. No terminal. No config files. No infrastructure knowledge.

How It Works

1

Choose channels

Select where your agent talks to you โ€” WhatsApp, Telegram, Signal, IRC, or any combination. The setup wizard walks you through authentication (QR code for WhatsApp, BotFather for Telegram, etc.).

2

Pick an LLM (or bring your own)

Choose a managed provider based on your data residency preference, or plug in your own API key. No model configuration needed โ€” we handle the defaults.

3

Start talking

Your agent is live. Send it a message on the channel you configured. It responds. It remembers. It learns your preferences over time. That's it.

What the User Gets

Personal AI on WhatsApp, Telegram, or Signal
Persistent memory across conversations
Channel-specific session history
Auto-reply when you message, proactive when it matters
No technical setup โ€” web UI for everything
Data residency control via LLM provider choice
Export your construct at any time (no lock-in)

Data Residency

LLM providers are hosted in specific jurisdictions. Users choose a provider based on where their data is processed โ€” matching their legal requirements and comfort level.

๐Ÿ‡จ๐Ÿ‡ฆ Cohere ยท Canada
๐Ÿ‡ซ๐Ÿ‡ท Mistral ยท France
๐Ÿ‡จ๐Ÿ‡ณ Zhipu ยท China
๐Ÿ”‘

Bring Your Own LLM

Cloud Hosting works with your own API keys too. Already have an OpenAI, Anthropic, or Ollama setup? Plug it in. The hosted agent uses your provider directly โ€” your prompts go to your account, not through us.

This is the self-hosted model, managed. Same framework, same channels, same memory โ€” we just run the binary for you.

๐Ÿ”—

Cloud Relay โ€” Connecting Disparate Networks

An agent running at home behind a NAT firewall. Another agent running on a cloud VPS. A third on a colleague's laptop. They need to share knowledge, coordinate tasks, and stay in sync.

Cloud Relay provides mesh nodes in our network that act as connectivity bridges. Agents connect outbound (no inbound ports needed). The relay routes messages between mesh members. All data is encrypted end-to-end โ€” the relay sees encrypted packets, never plaintext.

NAT traversal
E2E encryption
Multi-agent routing
Outbound-only connections
๐Ÿ’พ

Cloud Storage โ€” Syndicated Agent State

An agent's memory, identity, ontology, diary, and session history constitute its construct โ€” everything that makes it who it is. Losing that means starting over. Cloud Storage syndicates the construct to a secure node in our network.

Think of it as a mesh node with only syndication features. The agent pushes encrypted state snapshots on a schedule or on significant events. If the local instance is lost, the construct can be restored to fresh hardware. If you run agents on multiple machines, their constructs stay synchronized.

Encrypted snapshots
Disaster recovery
Multi-device sync
Construct portability

The framework is free. The network is optional.

Every premium service connects to the same open-source Animus kernel. No feature gates, no vendor lock-in. Self-host everything, or let us handle the infrastructure.