ELIO
Technical Architecture

Managed AI
Workspace.

How we deliver a fully configured AI operating system to non-technical business teams.

SSH + Remote MCP Self-Service Portal Per-Tenant Isolation Telegram Bot
01 - System Overview
Any AI client.
One company brain.
Any Client
CLAUDE DESKTOP
Code tab + SSH
CLAUDE.AI / MOBILE
Remote MCP over HTTPS
TELEGRAM BOT
REST bridge, any device
No servers on client
No credentials stored
SSH / MCP
Elio Server
Dedicated per client
AI RUNTIME
Claude Code
Business context
Skills library
Memory
INTEGRATIONS
Gmail
Calendar
Slack
Notion
HubSpot
Salesforce
Google Drive
Telegram
n8n
WhatsApp
Jira
+more
Elio AI
Orchestrates all services into a unified workspace
OAuth tokens encrypted, never leave server
APIs
Services
Google
HubSpot
Slack
Notion
Any API
manages
Self-Service Portal
app.getelio.co
Connect integrations Manage team Usage & billing
02 - User Journey
From zero to working
in four steps.
1
Sign up at getelio.co
Pick a plan, tell us your tools. We provision a dedicated server automatically.
~2 min
2
Connect integrations on portal
Open app.getelio.co. Click "Connect Google" → OAuth consent → done. One click per service.
~5 min
3
Connect your preferred client
Claude Desktop: Code tab → SSH.  Claude.ai: Settings → Add MCP server.  Telegram: /start in bot → authorize.
~3 min
4
Start working
"Draft follow-ups for all deals closing this month." AI has full access to every connected tool.
Ready
Access Channels
Connect from any
AI assistant.

The Elio Server exposes a Remote MCP endpoint over HTTPS. Claude clients connect natively. Telegram and other AI assistants connect via REST bridge — same company brain, any interface.

Claude Desktop
Code tab
→ Add SSH connection
→ Paste config from portal
Direct SSH tunnel
Full terminal + tools
Best for power users
Supported today
Claude.ai / Mobile
Settings → Integrations
→ Add MCP server
→ mcp.getelio.co/{tenant}
Remote MCP over HTTPS
OAuth 2.0, one-time auth
iOS / Android / Web
Roadmap Q2
Telegram Bot
/start in @elio_bot
→ authorize workspace
→ message = Elio task
No app install needed
Works on any phone
Team notifications
Roadmap Q2
MCP GATEWAY - HOW IT WORKS
CLIENT
Claude Desktop
Claude.ai
Telegram
→
MCP GATEWAY
mcp.getelio.co
HTTPS + OAuth 2.0
Tenant routing
→
ELIO SERVER
AI Runtime
Business context
All integrations
ChatGPT and Gemini do not natively support MCP. They connect via a REST bridge using GPT Actions (OpenAI) or Function Calling (Google). The Elio server exposes an OpenAPI-compatible endpoint for these integrations.
03 - Request Lifecycle
What happens when
a user asks a question.
USER
CLAUDE CODE
MCP SERVER
EXTERNAL API
"Find deals closing this month and draft follow-up emails"
READS CONTEXT
CLAUDE.md, memory, skill library. Understands the business. Plans tool calls.
CRM QUERY
hubspot.list_deals(
  close_date=this_month
)
GET /crm/v3/deals
?closedate=2026-03
→ 12 deals returned
GENERATES
Writes 12 personalized follow-up emails using deal context and tone from CLAUDE.md.
GMAIL
gmail.create_draft()
×12 drafts created
POST /gmail/v1/
users/me/drafts
×12 API calls
DONE
"12 follow-up drafts are in your Gmail. Review and send."
04 - Integration Flow
Connecting a new service.
Three clicks, zero engineering.
Click "Connect"
on portal
OAuth consent
authorize scopes
Tokens stored
on Elio server
Tools available
next session
// .mcp.json auto-updated on server { "google-workspace": { "command": "uvx", "args": ["google-mcp"], "env": { "CREDENTIALS": "/secure/tokens/google.json" } } }
// Token auto-refresh every 30 min { "access_token": "ya29.a0AfB_...", "refresh_token": "1//0eXq...", "expiry": "2026-03-14T12:00:00Z", "scopes": ["calendar", "gmail", "drive"] }
05 - Security
Per-tenant isolation.
Nothing shared.
TENANT A
Dedicated VM
Own SSH keys
Own OAuth vault
Own context & memory
TENANT B
Dedicated VM
Own SSH keys
Own OAuth vault
Own context & memory
TENANT C
Dedicated VM
Own SSH keys
Own OAuth vault
Own context & memory
SSH only
Key-based, no passwords
Encrypted
Tokens encrypted at rest
Audit log
Every action tracked
Region choice
EU / US / MENA
06 - Technology Stack
How app.getelio.co
is built.
Browser
app.getelio.co
FRONTEND
React 19
UI components
Vite 6
Build + HMR
Tailwind CSS
Styling
TanStack Router
Type-safe routing
TanStack Query
Server state + cache
Zustand
Client state
apiFetch() - retry, dedup, SWR cache, Bearer token
CADDY
TLS + reverse proxy + static
API
x2 instances, load balanced
Runtime Bun
Framework Hono
Auth Supabase Auth
Validation Zod
Assistant
Streaming LLM responses
Engine Claude API
Protocol SSE streaming
Container elio-assistant
Timeout 120s
Supabase
PostgreSQL + Auth + RLS
Redis 7
Cache + rate limits
BullMQ
Job queue + workflows
OBSERVABILITY
Prometheus Grafana Loki Tempo Promtail
PRIMARY LANGUAGE
TypeScript (strict) across the entire stack
API, worker, MCP server, frontend, CLI tools. Strict mode, zero any types. AI-augmented development with Claude Code.
07 - Scaling
Infrastructure roadmap.
1
0-50 CLIENTS
1 VPS per client
Hetzner Cloud VPS
Ansible provisioning
Manual onboarding
COGS ~$250/client
2
50-500
Kubernetes cluster
Container per tenant
Zero-touch provisioning
Auto-scaling
COGS ~$200/client
3
500+
EU
US
ME
Multi-region
Multi-region deploy
On-prem option
Skills marketplace
COGS ~$160/client
08 - Competitive Moat
Why this compounds.
MOAT
compounds
Context
CLAUDE.md grows
Integrations
more tools
Skills
industry playbooks
Memory
cross-session
The longer a client uses Elio, the more valuable it becomes. Context, memory, and skills accumulate. Switching cost grows every week. This is not a wrapper. It's a managed operating system that learns the business.
ELIO
getelio.co · Confidential · March 2026