Commercial
Pricing
DbFace can be commercialized in two delivery models: managed Cloud for fast team adoption and On-Premises for customers that require infrastructure control, private networking, or formal procurement.
Recommended commercial model: keep the core product easy to adopt, monetize managed operations and enterprise controls,
and avoid charging every report viewer when DbFace is used as an internal analytics layer.
Commercial packaging strategy
| Layer | What the customer buys | Suggested pricing logic |
|---|---|---|
| Cloud | Managed hosting, upgrades, backups, and faster rollout for business teams | Monthly subscription with builder seats included and generous viewer access |
| On-Premises | Self-hosted deployment, license activation, and data residency control | Annual license based on named users or builder packs |
| Enterprise controls | SSO, private connectivity, audit exports, SLA, and rollout assistance | Higher-tier plan or add-on, not bundled into entry pricing |
| Services | Migration, dashboard delivery setup, and custom Cloud Code onboarding | One-time implementation package or annual success plan |
Pricing principles
- Charge primarily for builders and admins, not every viewer, because internal analytics usually has many more consumers than authors.
- Keep Cloud as the default offer because it shortens evaluation time and reduces support cost.
- Use On-Premises to unlock regulated, private-network, or enterprise procurement deals rather than as the default first package.
- Reserve enterprise controls for higher tiers so entry plans stay simple and easy to understand.
Cloud plans
Recommended Cloud packaging for DbFace is workspace-based with included builder seats. This matches the product's value: teams building and publishing internal analytics pages while a larger group consumes them.
Cloud Launch
$99
per month
For early teams validating one workspace and a small set of reports.
- Up to 3 builder seats
- Managed hosting and upgrades
- Datasource setup and DSDL authoring
- Internal sharing and basic embed scenarios
- Email support
Cloud Team
$399
per month
Best default offer for analyst and operations teams shipping internal dashboards.
- Up to 10 builder seats
- Unlimited internal viewers
- Shared workspaces and report delivery flows
- Embed support for internal systems
- Priority support and onboarding help
Cloud Business
$999
per month
For organizations that need stronger controls, more builders, and a clear support path.
- Up to 25 builder seats
- Unlimited internal viewers
- SSO and centralized identity integration
- Audit-oriented controls and private connectivity options
- Service-level response commitments
Suggested expansion rule: sell additional builder packs separately so Cloud pricing can scale without forcing customers into a custom contract too early.
On-Premises plans
On-Premises should be positioned as an annual commercial license. It fits customers that need VPC-only access, restricted outbound networking, internal compliance review, or a slower enterprise buying cycle.
On-Prem Standard
From $12k
per year
A straightforward self-hosted license for internal teams that already run their own stack.
- Annual signed license key
- Up to 20 named users
- Customer-managed infrastructure and upgrades
- Deployment guidance and standard support
- Fits departmental or regional deployments
On-Prem Enterprise
Custom
annual contract
For security-sensitive, regulated, or large multi-team deployments.
- Higher user limits or multi-team rollout
- Enterprise identity and access requirements
- Audit, rollout, and environment management support
- Private-network or air-gapped deployment planning
- Premium support and migration assistance
Which model should a customer buy
| Situation | Recommended offer | Why |
|---|---|---|
| A fast-moving business or operations team wants to launch quickly | Cloud Team | Fastest onboarding, lowest support friction, and a clear monthly price point |
| A growing company needs more builders and centralized controls | Cloud Business | Adds governance and support without moving to a custom deployment too early |
| An enterprise requires private infrastructure or procurement-approved software licensing | On-Prem Standard | Annual licensing matches enterprise budgeting and infrastructure ownership |
| A regulated customer needs identity controls, rollout support, and private deployment constraints | On-Prem Enterprise | Turns infrastructure and compliance needs into higher-value commercial scope |
Add-ons and expansion revenue
- Additional builder seat packs for both Cloud and On-Premises.
- Implementation package for datasource onboarding, first dashboards, and delivery workflow setup.
- Premium support plan with faster response targets and rollout guidance.
- Custom Cloud Code or OEM-style embed projects for customers turning DbFace into part of their own product.
Recommended go-to-market path
- Lead with Cloud Team as the default plan for most inbound demand.
- Use Cloud Business to upsell teams that need governance and stronger support.
- Offer On-Prem Standard only when infrastructure control or procurement makes Cloud a blocker.
- Reserve On-Prem Enterprise for high-touch deals that can support annual contract value and services revenue.