What is Vox Pop Core?
Vox Pop Core is the MIT-licensed open-source engine behind voxpop.com — an audio-reply platform for podcasters, content creators, and anyone who wants their audience to talk back.
This repository (vox-pop-core) contains the open-core tier: the API surface, business logic, and shared types. The hosted product layers proprietary features on top.
What’s in the open core
Section titled “What’s in the open core”- Hono HTTP service at
apps/core-api/— the/api/v1/*JSON API surface. - Service bindings at
packages/core/— pure TypeScript services (UserService,PromptService,ReplyService,OrganizationService,FeedService, …) with pluggable dependency interfaces. Swap in your own backend without touching the route layer. - Shared types and Zod schemas at
packages/shared/— records, views, and request codecs. The same schemas validate the wire format and generate this API reference.
What’s intentionally not in the open core
Section titled “What’s intentionally not in the open core”- IVR / call-forwarding — Twilio integration, phone-number provisioning, carrier detection.
- Embed widget hosting — the iframe distribution layer for
<vox-pop-widget>. - Team and billing features — the hosted product’s organization-tier extensions.
These live in the closed-source layer that runs at voxpop.com. The open core is everything you need to run identity, prompts, replies, and the public API.
Who is this for?
Section titled “Who is this for?”- Self-hosters who want a turnkey audio-reply backend without depending on the hosted product.
- Contributors who want to extend the API surface, add new services, or swap the Firebase backend for something else.
- API consumers building mobile apps, embed widgets, or integrations against
api.phonicfactory.com.
Where next?
Section titled “Where next?”- New to the project? Read the architecture overview.
- Want to run it locally? Quick start.
- Building against the API? API reference.