vcon.store

A Home for Your VCONs

Hosted VCON storage, search, and auditing: the missing piece of the VCON ecosystem. Store, verify, and manage your conversation records in a privacy-first, consent-aware platform built on the IETF VCON standard.

Get Started →

What is a VCON?

A VCON (Virtual CONversation) is an IETF-standardised JSON container that captures everything about a conversation: voice, video, chat, SMS, WhatsApp, email, all in a single portable, verifiable record. Think of it as a vCard, but for conversations.

VCONs solve a problem that has existed since communications began: conversations happen across many channels, in many formats, siloed in many places. CDRs tell you a call happened. A VCON tells you everything about it: who was involved, what was said, what consent was given, what analysis was run, and proves none of it has been tampered with.

The Missing Piece

You can build a VCON today. But where do you put it? How do you know you're storing it correctly, auditing it properly, and handling redaction in a way that will hold up to compliance scrutiny?

That's what vcon.store is for.

It is a conserver-compatible VCON server built on the open standard, so you can send VCONs from any compliant tool and they will just work. No lock-in.

Key Features

🗄️ Storage & Indexing

• Store VCONs created by any VCON-compatible tool or pipeline
• Full indexing of the important parts of each VCON so you can search across your conversation records
• Free tier available. No subscription required to get started.

🔍 Search & Dashboard

• Browse and filter your VCON library from a clean dashboard
• See at a glance: parties involved, number of dialogues, analysis runs, call direction, and timestamps
• Play back individual call recording legs directly from the dashboard

📋 Audit Trail

• Every change to a VCON is logged: creation, amendments, patches, and redactions
• Full activity log per VCON showing the complete lifecycle

✂️ Redaction

• Manually redact personal information on demand
• Schedule automatic redaction: set a date and vcon.store removes the data when the time comes
• Redacted VCONs are linked to the original, preserving the audit chain without exposing personal data
• Share a redacted VCON with a third party; unique identifiers mean you can trace any data leak back to its source

🔔 Webhooks

• Get notified when things happen to your VCONs
• Integrate vcon.store into your existing pipelines and tooling

🔐 Privacy First, Consent Built In

• Consent metadata is stored within the VCON itself, not bolted on separately
• Compliant with the IETF VCON privacy primer's 10 principles
• GDPR friendly: UK data stays in the UK, US data stays in the US, completely isolated per customer

Kamailio Integration Example

vcon.store is designed to slot into real telephony stacks. Here's a typical flow using Kamailio and RTP Engine:

1. A call arrives and Kamailio routes it through RTP Engine, recording each leg independently
2. A VCON sidecar process listens for call events and creates the initial VCON at call start
3. Consent metadata (e.g. "this call may be recorded") is attached automatically
4. When the call ends, the recording is uploaded and the VCON is patched with the transcript from your AI provider of choice
5. The completed VCON is signed and sent to vcon.store via the standard conserver API
6. From there, you can view, analyse, amend, and redact it through the dashboard or API

Because vcon.store implements the open conserver spec, you can swap it for any other compliant server, or run your own alongside it.

Why Auditing is the Superpower

CDRs were built for billing. VCONs are built for truth.

With vcon.store you can demonstrate:

• Consent: that you had permission to record, what that permission covered, and when it expires
• Integrity: that the recording and transcript have not been altered since they were created
• Redaction: exactly what was removed, when, and why
• Deletion: that data was destroyed on schedule, with a record that it existed

This is what compliance actually requires. Not just that you stored a recording, but that you can prove the entire lifecycle of that conversation record.

Use Cases

Contact Centres & Customer Service

• Prove consent was obtained before every recorded call
• Share redacted transcripts with QA teams without exposing personal data
• Demonstrate compliance to regulators with a full, signed audit trail

AI Voice Agents

• Capture every conversation your AI agent has in a structured, searchable format
• Feed transcripts and sentiment back into your models with confidence in data integrity
• Attach consent records to every interaction automatically

Legal & Financial Services

• Meet record-keeping obligations with tamper-evident conversation records
• Redact PII on schedule without losing the business record
• Share verified conversation records with auditors or courts

Telecoms Providers

• Offer VCON-based conversation records as a value-added service
• Give customers portable, verifiable records of their calls
• Replace ad-hoc CDR exports with a structured, auditable alternative

Open Standard, No Lock-In

vcon.store implements the IETF VCON conserver specification. That means:

• Any VCON-compatible tool can send records to vcon.store
• You can also send those same VCONs to another conserver
• If you want to move, your data moves with you. It's just JSON

The VCON standard is actively developed at the IETF with three live drafts: the overview, the core, and the privacy primer.

Get Started

vcon.store launched at Kamailio World 2026. The free tier lets you start storing and exploring VCONs immediately.

Create Account →

vcon.store is developed by Everycast Labs Ltd. The VCON standard is developed by the IETF VCON working group.