Dashboard sign-in
LiveEmail sign-in for operators. Session cookies gate projects and the upload UI.
Sign in →What ships today, what is rolling out, and what we are building before and after the first public launch — dashboard, API, CLI, and voice sessions.
Available today — dashboard, API, and CLI for the same projects and builds.
Email sign-in for operators. Session cookies gate projects and the upload UI.
Sign in →Create a VoiceThere account from /signup with email magic link or GitHub, Google, or LinkedIn — no waitlist.
Docs →Sing in via GitHub, Google, or LinkedIn.
Create projects, upload verified agent bundles, and inspect build history from the dashboard.
Open dashboard →Set which build is active for a project or roll back to the previous release.
REST at /api/v1 for projects, builds, promote, and rollback — same contract as the CLI.
API reference →Published @voicethere/cli — login, build upload, deploy --wait, and promote. Pair with @voicethere/agent verify in CI.
npm →Roll out your active build from the dashboard or CLI — voicethere deploy --wait promotes and provisions managed voice workers.
Start a session from your backend; receive a join token and signaling URL for browser WebRTC. Async provisioning when workers scale up.
Test voice and text against echo agents from the project page, or paste an embed snippet with a client API key.
Start a voice session even when the microphone is denied or unavailable, switch input devices from the dashboard chat, and see an in-chat notice when permission is blocked (agent audio can still play).
Invite teammates, assign org roles, and restrict projects to specific members from the dashboard.
Immutable trail of API and dashboard actions — browse org-wide or per project.
Session counts, billable minutes with monthly allowance progress, and error rate on each project.
Project-scoped STT/TTS latency (p50, p95, p99), utterance volume, barge-in rate, and VAD transitions on the Usage Voice tab and API — only your project's data.
Docs →Printable credit breakdown by project and usage kind, plus links to Stripe hosted invoices for subscription and metered overage cash charges.
Billing docs →Flat monthly plans via Stripe Checkout and Customer Portal. Subscribe, assign subscriptions to projects, and buy multiple slots of the same tier.
View plans →Each tier includes a monthly billable-minute allowance. Usage is tracked per project; new sessions are blocked at the limit, with grace before hard disconnect.
Paginated session list per project with status, duration, and billable seconds — same records as CLI sessions list and billing queries.
Several clients in one session with shared or per-peer agents. Disable voice for DataChannel-only apps — games, live sync, and chat without STT/TTS.
Configure idle timeouts, data-only mode, shared vs per-peer agents, and cloud voice providers from the dashboard or CLI.
Docs →Structured errors from agents and workers in the dashboard — filter by session and map codes using the public error catalog.
Error catalog →Write structured agent logs and search them in the dashboard — filter by message, level, and fields per project or session.
Searchable structured logs from agentLog and console.* — filter by message, level, and JSON fields. Session failures persist as error-level lines with stable codes and soft rollover. Paid overage past the monthly included cap bills usage credits (1 per 1,000 entries) when overage billing is on.
Logging guide →Developer documentation at /docs — quickstarts, API reference, session guides, agent environment, secrets, deploy flow, and package install instructions.
Open docs →Search developer documentation by keyword and browse guides grouped under Guides and Help on /docs.
Open docs →Try voice and multiplayer examples from the marketing site — landing chat launcher, showcase catalog, and a shared-world board visitors can spawn on together.
Try demos →Product blog and email newsletter at /blog — release notes, guides, npm updates, dashboard features, and platform news.
Read blog →Starter templates include matching client-side UI alongside the agent bundle. Hosted client assets are served from a global CDN and cache-purged when you deploy a new build so browsers pick up the latest embed or demo code.
Docs →Advanced and Ultimate projects get a private Redis instance for your agents — credentials injected at start. Sync game state, lobbies, and context across every concurrent session worker in the same project.
Docs →POST HTTPS to your project URL — the platform fans requests to every ready session worker. Verify signatures in your agent; warm pool keeps a replica ready between sessions.
Docs →Fine-tune STT/TTS, barge-in, and related voice behavior from the dashboard or API — beyond basic provider selection.
Docs →Component health for voice and related services — operators and customers can check platform status.
Status →Relay servers included in session mint responses — reliable calls through firewalls and NAT.
Ensure that every paid tier has guaranteed resources in the cluster, free tier can be queued or not available.
Set max concurrent sessions by STT/TTS choice — local/self-hosted voice uses more compute but costs less, so subscription tiers expose different concurrency caps than cloud vendors.
Browse past STT and TTS turns from the dashboard — stored encrypted, with PII masked where possible. Only speech recognition and synthesis events are logged; DataChannel messages are out of scope.
Docs →Opt-in voice-session audio with dashboard playback, included minutes per plan, rollover bank or metered overage, and agent start/pause/resume/stop for sensitive moments.
Docs →On the roadmap after the first public launch — multi-region, advanced voice ML, and deeper operator tooling.
Complete quickstart, API reference, browser client guide, and deploy runbooks at /docs.
Early docs →Real-time event stream while a call is in progress — connect to the session websocket and receive events like agent speak, chat, and binary sync.
Dynamic audio mix groups within a session — reassign who hears whom mid-call for team games and breakout voice.
Multi-region EU, US, and APAC — regional deployments for a lower latency
Optional Krisp-powered turn-taking and interruption prediction for smoother conversations — enable when you need ML-grade voice activity and barge-in beyond the default energy VAD.
Create and belong to more than one organisation, then switch between them from a dropdown in the dashboard.
Expand the sandbox allowlist so agents can use selected LLM SDKs and other Node packages. Reach out and tell us which packages you need — we will add them to the whitelist or set up an npm install flow.
Edit agent code directly in the dashboard for quick fixes, with a validation flow that checks the new code still matches the defined agent protocol and expected behavior before you ship.
Dashboard embed snippet works today; standalone npm package, theming, and one-line install polish before public launch.
Predefined voice-agent templates with a basic system prompt wired through STT/TTS — pick a use case, pass your LLM API key, and the agent starts talking without custom glue code.
Set a custom customer identifier from agent code, then find and group that user’s sessions via CLI or API — conversation history for returning customers, with client and agent examples.
Register HTTPS webhook URLs that VoiceThere delivers into your running session workers — payments, CRM events, or custom integrations reach the same process that owns the voice call.
Optional filtering on recognized speech and agent replies — redact or block flagged phrases before they reach the far end, transcripts, or conversation history.
Spatial audio mixing for voice+data sessions without STT/TTS — position players in the mix for multiplayer and other realtime experiences.
Join a Google Meet as listen-only, transcribe the meeting, and produce a summary — useful when the agent should observe without speaking.
Enable or disable speech-to-text from agent code on voice+data sessions — turn recognition on for meeting summaries and space notes, or off when you only need media and data.
You can change your choice anytime via Cookie settings in the footer.