Skip to main content
Cloud voice & agent runtime

Cloud voice & agent runtime for AI assistants that speak, remember, and use tools.

Assistant Core is the cloud runtime layer for voice, reasoning, memory, knowledge base, and tool calling across web, apps, smart devices, IoT, and robots.

Voice RuntimeTool CallingMCP LayerKnowledge BaseLong-term MemoryDevice-ready
Assistant Core running across web, app, embedded widget, watch, and voice device surfaces
Market problem

A chatbot demo is easy. A production assistant is much harder.

Once your assistant needs to listen, speak, remember, call tools, understand private data, and run on real devices, teams end up stitching many infrastructure layers together.

Realtime voice is more than TTS

A natural voice experience needs VAD, ASR, LLM, TTS, audio streaming, interruptions, and latency control in one pipeline.

Agents need actions, not only answers

The assistant must call APIs, read data, trigger workflows, control devices, and extend through MCP or governed tool calling.

Small devices cannot run large models

Smart devices, robots, and IoT hardware should keep microphone, speaker, sensors, actuators, and connectivity while the cloud runtime handles reasoning, memory, and voice.

Real products need safe operations

Multi-tenancy, auth, permissions, conversation history, memory, and observability need to ship with the assistant from day one.

Runtime layers

One unified runtime layer for assistants that speak and act.

Assistant Core brings the hard parts of voice, agents, tools, and device integration into one assistant-level architecture.

Explore runtime

Assistant Intelligence

Shape the prompt, model stack, knowledge base, long-term memory, brand voice, domain, and behavior for each assistant.

PromptModel stackKnowledge baseMemoryBrand voice

Voice Runtime

Customize the voice pipeline from VAD, ASR, LLM, and TTS to realtime speech-to-speech for web, apps, or screenless devices.

VADASRLLMTTSRealtime voice

Tool & MCP Layer

Connect the assistant to APIs, data, workflows, internal systems, smart homes, or robots through tool calling and MCP.

Built-in toolsCustom APIsMCP serverDevice tools

Integration Layer

Embed the assistant into products through Chat API, Voice WebSocket, MQTT gateway, widgets, or custom hardware.

Chat APIVoice WebSocketMQTTEmbedHardware

Operation Layer

Manage assistants, users, conversations, memory, devices, access control, and production operations.

UsersConversationsDevicesRBACObservability
Use Cases

One runtime for several product teams.

Assistant Core fits products where assistants need to speak, remember context, call tools, and connect to software or devices.

Developers & SaaS

Integrate an assistant into landing pages, apps, docs, dashboards, or SaaS products through API, WebSocket, and embedded widgets.

Businesses

Build internal assistants for support, sales, HR, training, knowledge management, and workflow automation on private data.

Creators & experts

Turn expertise into a virtual assistant for students, communities, customers, or followers with private memory and knowledge base.

Smart devices & robots

Bring voice assistants to education robots, smart toys, smart home devices, learning hardware, kiosks, or compact AI hardware.

Core capabilities

The capabilities a production assistant needs.

Assistant Core is more than a chat UI. It provides the layers needed for private knowledge, memory, tool calling, realtime voice, and safe production operations.

Assistant Intelligence

Control system prompt, model stack, knowledge base, tools, MCP connections, behavior, and access for each assistant.

System PromptRBACMulti-tenantMCP

Knowledge Base

Connect documents, websites, and structured sources so answers stay tied to the information your team trusts.

PDF / DOCXWeb URLspgvector

Voice Runtime

Voice pipeline VAD → ASR → LLM → TTS with audio streaming for natural spoken conversations.

< 1sOpus Audio

Tool Calling & MCP

Let the same assistant call built-in tools, custom APIs, server MCP, endpoint MCP, and device-side MCP tools.

MCPCustom APIs

Device Experience

Customize interface, fonts, emoji, wake word, and backgrounds, then deploy to smart devices, IoT hardware, or robots.

MQTTWake WordEdge

Long-term Memory

The assistant remembers context across sessions, extracts important facts, and retrieves them through pgvector when needed.

Long-termCross-sessionpgvector
Provider ecosystem

Choose providers per layer of the voice pipeline.

Mix models for reasoning, ASR, TTS, realtime voice, or embeddings based on each assistant's needs.

OpenAI
OpenAI
Anthropic
Anthropic
Google
Google
xAI
xAI
DeepSeek
DeepSeek
Xiaomi
Xiaomi
ElevenLabs
ElevenLabs
Soniox
Soniox

Provider availability depends on deployment configuration and workspace API keys.

Security & operations

Assistant runtime needs security at the request layer.

Voice, memory, tools, and device integrations all pass through authentication, authorization, tenant isolation, and operational observability.

Layer 1

Transport Security

TLS 1.3 encryption on all HTTP, WebSocket, and MQTT connections. No plaintext data in transit.

Layer 2

Authentication

JWT access + refresh tokens, Google/GitHub OAuth with HMAC-signed state and Redis-backed nonce to prevent replay attacks.

Layer 3

Authorization & RBAC

Role-based access control with scoped JWT claims. Per-assistant permissions and multi-tenancy isolation at the request level.

Layer 4

Data Security

Encryption at rest via PostgreSQL and S3 server-side encryption. Row-level isolation between tenants.

Layer 5

Network Security

Per-user and per-IP rate limiting. CORS policies. DDoS mitigation at the load balancer layer.

Layer 6

Audit & Observability

Request logging, conversation-level LLM/tool traces in the admin dashboard, and assistant metrics for security monitoring.

TLS 1.3JWT / OAuth 2.0RBACpgvectorRedis NonceLLM Traces
Blog

Insights from the team

Technical deep-dives, product updates, and best practices for building AI-powered products.

View all posts
VoiceMay 22, 2026

AEC: Why AI Voice Assistants Need Echo Cancellation

Explaining Acoustic Echo Cancellation from the NLMS algorithm to real-world deployment in the browser (AEC3) and on ESP32 (ESP-ADF). Includes a comparison of AEC support across OpenAI, Gemini Live, and xAI Grok.

ArchitectureApr 15, 2025

Building a Real-World RAG Pipeline with pgvector

How we built a retrieval-augmented generation pipeline handling PDF, DOCX, and web URLs with chunking, embedding, and cosine search — reaching 91% accuracy compared to 34% with a plain LLM.

IoTMar 28, 2025

MQTT + UDP: Bringing AI Down to Edge Devices

Why we dropped WebSocket for hardware devices and moved to MQTT + UDP — cutting latency from 380ms to 165ms, RAM from 45KB to 12KB, and gaining 40% battery life.

ArchitectureMay 22, 2026

Multi-LLM Architecture: 6 Providers, 14 Models, 1 Codebase

How we integrated OpenAI, Anthropic, Google, xAI, DeepSeek, and Xiaomi through native SDKs — letting users switch models mid-conversation, saving up to 90% on input-token costs with prompt caching, and deploying with zero downtime.

Ready to build an assistant that speaks and acts?

Start with one assistant, then configure prompt, voice pipeline, memory, knowledge base, tool/MCP connections, and deployment surfaces for your product.