Evaluation scope
Start from the workflow you need to prove first.
Pricing and deployment
Choose the rollout model that fits your workflow
Pricing depends on workflow scope, deployment shape, and the controls your team needs. This page is organized around those choices, not seat-count theater.
- Start small without dead ends
- Tie price to operating shape
- Plan for enterprise standardization
Needs in
Deployment need
Cloud, private, or embedded rollout changes the track.
Render path
Adoption path
Match deployment shape and workflow scope before talking about plan names.
- 01Evaluate fit
- 02Deploy cleanly
- 03Expand usage
Rollout out
Deployment option
Choose the operating model your team can support.
Expansion path
Move from first team to broader rollout without a reset.
Pricing works better when it is tied to rollout shape and ownership, not a pile of disconnected labels.
How to evaluate: Start with template complexity, deployment boundaries, and who will run the workflow after rollout.
Team Evaluation
For teams proving out templates, authoring speed, and the first delivery workflows.
Interactive studio access
Template versioning
Preview and testing workflows
Initial implementation guidance
Operational Production
For organizations moving quotes, reports, statements, and packs into daily production.
Async render automation
Batch output and webhook flows
Permission-aware operating model
Deployment architecture guidance
Enterprise Platform
For teams standardizing document delivery across products, business units, or regulated environments.
Private deployment options
Extensibility and plugin strategy
Security and compliance alignment
Architecture review and rollout planning
Deployment models
Private, self-hosted, and embedded rollout options
Packaging only matters if the deployment model can pass security review, operating review, and team reality.
Private Cloud
Run the product inside controlled infrastructure without changing the user workflow.
Self-Hosted
Deploy with clear service boundaries for the app, workers, storage, queue, and converters.
Embedded Platform
Embed generation into your product without assembling the full document stack yourself.
Included in evaluation
Architecture review
Walk the current rendering pipeline, data model, and governance constraints.
Template fit check
Validate format coverage and identify the fastest proof points for your document inventory.
Rollout guidance
Map the path from evaluation into governed production use.
Next Step
Start with the packaging model that matches your operating reality
Pricing becomes clearer once we understand template complexity, deployment boundaries, document volume, and rollout goals.
In the session