Enterprise & pricing
No per-seat math, no usage meters, no tier maze. Self-host the realtime backbone for free; license the Platform and bring in our engineers when production is on the line — all through a single contact.
Open Source
The complete realtime backbone. No feature gates, no seat counts, no usage meters.
Platform & Enterprise
The commercial application platform — plus the team that built the stack working alongside yours.
What the engagement includes
Every engagement is scoped with the core team: architecture, migration, performance evidence, training, and support coverage.
We map PrivChat onto your app, traffic shape, compliance requirements, and existing identity systems — before you commit.
Move off a hosted IM vendor or an in-house socket service incrementally. No big-bang rewrite required.
Reproducible load tests on your target hardware, published numbers, and bottleneck tuning before production launch.
Training, implementation reviews, and a dedicated engineering channel connecting your team to ours.
Production plan
A proven sequence from first assessment to a supported production launch — incremental, measured, and reversible at every step.
Map traffic, auth, data ownership, compliance, and existing chat dependencies.
Move features incrementally through SDK, server, and platform module boundaries.
Run reproducible load tests and tune reconnect, sync, storage, and gateway behavior.
Go live with escalation paths, upgrade plans, and a dedicated engineering channel.
Questions
If your question is not here, ask it on GitHub or write to contact@privchat.dev — both routes reach engineers, not a sales script.
No. The server, SDKs, and protocol are the same code we run in production, with no gated features or usage meters. The commercial product is the Platform — the application layer (wallet, payments, games, admin) built on top of the open backbone.
Per deployment, source-available to licensees, self-hosted on your infrastructure. You get the source of the modules you license — no black boxes in your money path.
Not yet. A managed cloud is on the roadmap; today everything is self-hosted by design. If you want us to operate it with you, that is part of the engagement conversation.
Yes — GitHub issues and discussions are actively maintained, and community-reported bugs are triaged like any engineering work. A contract adds guarantees: SLAs, dedicated channels, and scheduled engineering time.
Get in touch
One address, no routing maze: developers and enterprise teams both reach the core engineering team at contact@privchat.dev — no marketing call, straight to architecture.
