Assemble
Usage
For teams injecting the SDK into one or two surfaces.
- Per-message metering with a monthly floor
- Overlay and full-screen modes
- BYO LLM pass-through
- Community docs and standard adapters
Pricing
Price the work, not a vague seat.
Chat infrastructure has mixed unit economics. Essenize is designed around five levers: per message, monthly users, clubbed volume, LLM charges, and infrastructure. Packaged plans below are starting points; production contracts mix the levers that match your traffic.
Compile
Volume
Clubbed volume records for production chat across channels.
- Committed message + MAU bundles
- Templates, flow builder, streaming API
- Analytics API and panel
- WhatsApp, Slack, Discord, webhooks
Sovereign
Infra
Self-hosted Docker runtime with itemized infrastructure.
- You absorb or Restora operates the cluster
- BYO database and existing chat backends
- Observability panel on your instance
- Security review and deployment engineering
How the levers combine
| Lever | When it dominates | Notes |
|---|---|---|
| Per message | Transactional support, notifications, high fan-out | Cleanest unit when threads are short |
| Monthly users | Companions, copilots, internal seats | Better when a person opens many sessions |
| Clubbed volume | Forecastable enterprise traffic | Committed records, overage on the same meters |
| LLM charges | Any generative completion | Pass-through to your endpoint, or billed if Restora routes |
| Infrastructure | Self-hosted and dedicated cloud | Compute, egress, and observability footprint |