Pilot
Prove a representative report before planning a wider rollout.
Let’s define it.
- Agreed use case and sample report
- Datasource and export acceptance
- Roles and access review
- Documented next steps
PRICING & ENGAGEMENT
Start with a scope.
Not a surprise.
Tell us how you plan to use reporting. Deployment, users, integrations, and support are discussed before a commercial commitment.
On-premises
A scoped deployment for organizations managing their own infrastructure.
Contact sales
- Deployment requirements review
- Backup and recovery planning
- User and report-access model
- Agreed support arrangements
Embedded
Plan an integration around your application and authorized readers.
Contact sales
- Report and API use-case review
- Allowed origins and permissions
- Output and parameter requirements
- Integration acceptance plan
Engagement options for discussion. No public price, SLA, or unlimited-usage commitment is stated. Commercial terms require an approved quotation.
GOOD QUESTIONS
Before you get started.
Can we try it with our own report?
Start with an agreed pilot scope. Use approved, non-sensitive sample data for initial evaluation, then plan authorized customer datasource acceptance.
Is an on-premises deployment available?
On-premises deployment is the current focus. Server compatibility, installation, security, and operational ownership are validated for each installation.
Are Word, Excel, and PDF identical?
No. Use PDF for print fidelity. Word supports editable text and tables with some elements embedded as images; Excel options serve different data and layout needs.
Does the website create an app account?
No. This marketing site is separate from the reporting application. Application accounts are provisioned and governed within the app.
Is email delivery included automatically?
Email delivery needs SMTP configuration and an authorized delivery test. Availability and support are agreed as part of deployment acceptance.