Rynko Reporting
Rynko Reporting generates formatted Excel and PDF reports from your own databases on a schedule, and delivers them by email, Teams, Slack, or file share.
It is built for teams replacing IBM Cognos, Crystal Reports, or a pile of hand-maintained SQL scripts — where the reports must look exactly right, run unattended, and never require exposing a production database to a SaaS vendor.
How it works
Reporting has two halves:
The agent runs on your infrastructure. It holds your database credentials, executes the queries, and renders the finished documents locally using the same template engine as Rynko Render. It is a single binary or Docker container — no JVM, no Metabase, no separate reporting server.
The control plane is the Rynko webapp. You design reports, write queries, set schedules, and read run history there. It never sees your database credentials or your query results.
The two connect over a single outbound HTTPS connection from the agent. There are no inbound firewall rules to open, no VPN, and no IP allowlist.
Your network Rynko
┌────────────────────────────────┐ ┌──────────────────────────┐
│ Reporting Agent │ │ Control plane │
│ │ │ │
│ • Query engine (native │ SSE │ • Report + query design │
│ Oracle/Postgres/MySQL/ │ ─────► │ • Schedules and jobs │
│ MSSQL drivers, DuckDB │ config │ • Run history │
│ for CSV/TSV) │ │ • Template designer │
│ • Render engine (PDF/Excel) │ ◄───── │ │
│ • Scheduler │ runs │ │
│ • Distribution │ │ │
│ │ │ │
│ ▼ your databases │ │ │
└────────────────────────────────┘ └──────────────────────────┘
Because the query engine and the renderer both live in the agent, reports keep running when the internet connection drops. Runs are queued locally and reported back when the link returns.
What you get
| Capability | Detail |
|---|---|
| Data sources | Oracle, PostgreSQL, MySQL, SQL Server, and CSV/TSV files |
| Query building | SQL editor with schema discovery, or composed query objects with reusable filters and parameters |
| Templates | The same visual designer used for Render — including a spreadsheet-style grid component built for report layouts |
| Output | Excel (.xlsx) and PDF, from one template definition |
| Scheduling | Cron schedules on the agent, plus multi-report jobs and on-demand runs |
| Distribution | Email (SMTP), Microsoft Teams, Slack, and file share |
| Cognos migration | Import Cognos report specifications and turn them into editable Rynko templates |
| Data sovereignty | Credentials and result sets stay inside your network |
Where to start
- Getting started — register an agent and run your first report end to end
- Agents — install, configure, and operate the agent
- Datasources — connect databases and file sources
- Migrating from Cognos — import existing report specifications
Pricing
Reporting is included in every Rynko subscription. Documents generated by reports draw on the same monthly document allowance as Render. The number of agents you can run is what varies by tier — datasources, query objects, reports, schedules, and jobs are unlimited on every plan. See Limits & Quotas for the current caps.