Editorial view: product surfaces, runtime boundaries, and deployment shape at a glance.
Product surfaces
| Surface | What it does |
|---|---|
app.ara.so | Main user experience (desktop-like apps, chats, file tooling, controls). |
api.ara.so | Authenticated cloud API for session lifecycle, files, skills, credentials, usage, and realtime proxying. |
| Sandbox runtime | Per-user isolated environment where the agent runtime, channel bridges, and tool execution run. |
ara.so | Marketing + public docs surface. |
What makes Ara different
- Private runtime per user with persistent workspace.
- Skills-first behavior with auto-create and reuse loops.
- Cross-channel assistant continuity.
- Message and file co-presence for real work.
- Browser-native autonomous execution.
Capability map
Sandboxing
Isolated runtime with persistent storage.
Skills
Discover, install, and auto-create patterns.
Learning loop
Memory + refinement loop.
Messages + files
Unified data path.
Browser agents
Browsing, automation, and extraction.
Multi-agent teams
Delegation for parallel specialist work.
Communication channels
Ara supports channel workers and bridges for:- Telegram
- Signal
- iMessage (desktop bridge) and Linq (iMessage/RCS/SMS cloud path)
Integration model
Ara uses MCP to connect external tools. Integrations can be injected per session and surfaced to the runtime either directly or via discovery/unlock strategies.Integrations and MCP
See how tool access is granted, scoped, and executed.