The stitched stack vs. one ecosystem
One comparison, eight concerns. The stitched stack — a dozen DIY open-source projects and SaaS vendors, each its own identity model and audit trail, data leaving your perimeter, seams you own forever — vs. the one self-hosted Visca ecosystem: one identity model, one audit trail, open-weight models in-perimeter, nothing that calls home.
Real-time conversational agents — call centers, intake, patient ops, customer service, collections. Latency-sensitive, often PHI- or PCI-handling.
Describes the generic stitched-stack pattern in this category. No specific product is named or evaluated.
Identity
SigilA voice agent runs as a tenant on a hosted vendor — one of several in the stack. Whoever holds the API key issues calls, and the call already left your perimeter to reach it. There is no per-call root of trust — no cryptographic identity bound to the caller, the agent persona answering, or the consent captured on this call.
Every call mints a Sigil bound to the caller, the agent persona, the runtime, and the consent record. Two calls from the same campaign are cryptographically distinct. Revocation propagates mid-conversation.
Credentials
WarrantEHR session tokens, CRM credentials, payment processors, and SMS providers sit in the agent's tool config for the life of the deployment. One call's prompt injection — via DTMF, via a hostile caller — is access to everything.
Every mid-call tool reach is a Capability Grant — scoped to caller, verb, resource, and duration. Read-PHI for this caller, for sixty seconds, with consent on file. Nothing reusable.
Discovery
PlexusDownstream telephony carriers, STT/TTS providers, and tool endpoints are hardcoded per environment. Failover is a redeploy. Latency is whatever the last config push produced.
STT, TTS, telephony, and tool providers resolved through Plexus by capability descriptor. Failover is a policy change. Latency targets enforced per call.
Declarative state
CastVoice personas, scripts, voice settings, allowed phrases, and tool lists are configured in vendor UIs. Two regions drift apart silently. There is no plan, no diff, no rollback.
Personas, voices, scripts, tools, and safety guards declared in Cast. Plan, apply, diff. Same persona, every region, every campaign, by design.
Packaging
SealA persona is a snapshot of UI state. Yesterday's persona is rarely reproducible. Voice version, prompt revision, and tool swaps flow through different channels with no unified versioning.
Each persona is a Seal Bundle pinning the voice, the prompts, the tool list, the model versions, the safety policies — content-hashed, Sigil-signed. The call from last quarter is one hash away.
Runtime
Lattice RuntimeThe platform decides per-call duration, fallback, and cost. Cost ceilings appear in monthly invoices, not at the call layer. A model rate-limit becomes a dropped call.
Lattice Runtime runs every call under per-call budgets with model and provider fallback. Durable execution survives a process death mid-call. Costs governed in real time, not in arrears.
Audit
ChronicleCall recordings sit with one vendor, transcripts in another's schema, tool calls in scattered logs — a separate audit trail per part of the stack. Proving consent was captured before this PHI access is a forensic exercise across vendors.
Chronicle records the consent, the transcript, every tool call, every model invocation — all Sigil-keyed and cryptographically chained. Consent-to-action is a single query, SIEM-exportable.
Dev surface
PraxisOne vendor's UI for persona authoring, a separate SDK for tool integration, a separate analytics dashboard, a separate eval framework — every part its own login. Each voice agent is its own stitched mini-stack.
Praxis authors the persona, runs evals against recorded calls, deploys, observes — one CLI, one set of primitives, identical to every other agent category in the estate.
How to read this
The stitched stack leaves the same gaps open for regulated buyers across every layer: identity, credentials, discovery, declarative state, packaging, runtime, audit, and the developer surface. A dozen separate projects and vendors, each its own auth and upgrade cycle, each a seam you own forever. Visca closes them as one cohesive ecosystem — not eight tools you stitch.
The work itself doesn't change. The same voice, clinical, browser, document, embodied, and coding workloads run exactly as before. What changes is the substrate underneath — one identity model, one audit trail, open-weight models in-perimeter, nothing calling home. Identity is cryptographic, credentials are ephemeral, audit is one chain, and the answer to "who did what" is a query.
See it in your environment
Visca Cloud is the fastest way to put the whole ecosystem — Trust, Lifecycle, and Record — in place of the stitched stack you maintain today.