Support

ReportBridge is a drop-in replacement for SSRS that runs standalone or inside Domo. It renders your existing RDL reports natively — both original TSQL reports against SQL Server and AI-converted reports against PostgreSQL — in a unified viewer with group-based access control. You can view your TSQL reports on day one, then migrate to PostgreSQL at your own pace with side-by-side data validation.

ReportBridge is designed for enterprises with large SSRS report libraries (50 to 500+ RDL files) who cannot afford to rebuild every report in a dashboard tool. It is especially relevant for Domo customers, regulated industries where report format is dictated by regulatory bodies, and organizations migrating from SQL Server to PostgreSQL.

ReportBridge supports paginated reports defined in RDL and RDLC format — the standard file format used by Microsoft SQL Server Reporting Services. Report layouts, groupings, page breaks, headers, footers, sub-reports, matrix structures, and parameterization all transfer without modification.

SQL Server Reporting Services (SSRS) is Microsoft’s paginated reporting engine, used by an estimated 100,000 to 150,000 organizations worldwide. Microsoft has confirmed that SSRS will not receive new versions — SQL Server 2025 ships with Power BI Report Server instead — leaving organizations to migrate to Power BI, rebuild reports in another tool, or remain on aging infrastructure. ReportBridge provides a fourth option: preserve existing reports while exiting the Microsoft ecosystem entirely.

It genuinely is: SSRS 2022 gets security patches through January 11, 2033, and Microsoft is not forcing anyone off it before then. But that date rarely covers a whole situation — SQL Server 2016 extended support already ended July 2026, 2017 and 2019 follow before 2033, the RDL/T-SQL talent pool keeps shrinking, SQL Server and Windows licensing (often $50K+/yr) keeps costing money every year you wait, and migration cost compounds the longer an estate sits.See the honest, no-invented-deadline breakdown →

ReportBridge connects four layers into a single migration pipeline: (1) an Admin app for uploading and AI-converting RDL files, (2) a publish step that deploys converted files to the report server on AWS, (3) a render step where the report server reads the RDL natively and queries PostgreSQL, and (4) a Viewer that renders the report standalone via the web app, or embedded inside a Domo card through a Domo Everywhere iframe. All external operations route through an AWS Lambda API bridge.

Your original RDL files are uploaded to the Admin app, where an AI-assisted converter rewrites the embedded T-SQL queries to PostgreSQL syntax. The report layout, formatting, parameters, and visual structure remain untouched — only the SQL queries inside the RDL are modified. You can download the converted RDL files at any point.

No. The report server reads existing RDL / RDLC files natively, so no layouts are rebuilt. The only changes made to your report files are the SQL query conversions from T-SQL to PostgreSQL and the data source connection strings.

ReportBridge supports both SQL Server and PostgreSQL simultaneously. Original TSQL reports can be published directly against SQL Server for immediate viewing. AI-converted reports run against PostgreSQL. The Viewer shows both in a unified interface, and the Validation screen compares data across both sources side by side. Multiple databases per deployment are supported with per-datasource mapping and alias resolution for multi-jurisdiction environments.

Yes. The Legacy Reports screen in the Admin app publishes your original SSRS reports directly against SQL Server with zero conversion. ReportBridge rewrites the RDL data source credentials into the format the report server expects, but the SQL queries are untouched. Your reports render exactly as they did in SSRS, and users can view them in the Viewer immediately — standalone or inside Domo.

ReportBridge appears as two Domo apps: a Viewer app that end users interact with (featuring category navigation, search, and embedded paginated reports) and an Admin app for administrators to manage conversion, publishing, and access control. Both run as native Domo ProCode cards -- available today as standalone web apps at report-bridge.com/app, with a one-click Domo Marketplace listing coming soon.

No. End users access reports through their existing Domo login. The Viewer app authenticates through Domo Everywhere, and no separate credentials or accounts are required for report viewing.

Access control is enforced server-side using Domo groups. The Admin app reads your existing Domo groups directly and lets you map them to reports with a checkbox interface. The Lambda API filters the report list so that each user sees only the reports their groups are authorized to view. Access is fail-closed: if no groups are assigned, the user sees no reports. There is no separate permission system, user directory, or login to manage.

The Admin app sends each T-SQL query to Claude AI along with the relevant PostgreSQL schema context (table and column definitions). The AI rewrites the query to PostgreSQL syntax, handling patterns like ISNULL to COALESCE, TOP N to LIMIT N, GETDATE() to NOW(), DATEADD to interval arithmetic, and hundreds of others. Converted SQL is then validated via EXPLAIN against the live PostgreSQL database.

Roughly 90% of queries convert on the first attempt (90.6% base rate on our 331-dataset production baseline); the iterative test/fix loop (up to three rounds per query) catches most of the rest, reaching a 95.8% effective conversion rate on the full ~190-report production corpus. Reports with highly complex SQL constructs like PIVOT, DECLARE, or recursive CTEs may require manual review with the built-in correction tools.

It is a dataset-level measure, not a report-level one. A single RDL can contain several datasets (individual SQL queries), and the rate counts datasets, not whole reports. A dataset counts as converted when its generated PostgreSQL survives an EXPLAIN plan check and then a LIMIT 1 execution against a live PostgreSQL database — after the automated test-and-fix rounds have run. Our published 95.8% is 317 of 331 scorable datasets across a 190-report production library (baseline measured 2026-04-25). Two honest caveats: it measures whether the query runs, not that its results match SQL Server row-for-row — that is a separate data-parity step — and it is our historical rate on our own corpus, not a prediction for your estate.

The report server supports a subset of VB.NET expressions commonly used in SSRS reports, including standard formatting, conditional visibility, and calculated fields. Complex custom assemblies or code blocks that reference external .NET libraries may require manual adjustment. The AI conversion focuses on SQL queries; report-level expressions are preserved as-is in the RDL file.

ReportBridge is a fully managed SaaS platform — all infrastructure (report server, Lambda, RDS, load balancer, monitoring, backups) is hosted and managed by ReportBridge. The only things you provide are: (1) network access to your existing PostgreSQL or SQL Server databases so reports can query your data, and (2) optionally, your own Anthropic or AWS Bedrock API keys for AI-powered SQL conversion. Everything else is included in your subscription.

Yes. ReportBridge connects to any PostgreSQL database that is network-accessible from our AWS environment. Your database can be on AWS, Azure, GCP, or on-premises — it just needs to be reachable over the network. We will work with you to configure any required firewall rules or VPN connectivity during onboarding.

ReportBridge supports on-premises PostgreSQL and SQL Server databases as long as they are network-accessible from our AWS environment via VPN, Direct Connect, or public IP with firewall rules. ReportBridge manages all connectivity configuration on our side. Your database stays where it is — we just connect to it for report rendering.

The ReportBridge Report Server is a fully managed RDL rendering engine that natively reads and renders your SSRS RDL / RDLC files. It is the only commercially available engine that can render SSRS paginated reports without SQL Server or Windows Server. ReportBridge hosts, operates, and maintains the report server on your behalf — you never need to install, configure, or update it.

The report server license cost is included in your ReportBridge subscription. ReportBridge manages the licensing relationship with the report server vendor directly. You do not need to procure, install, or manage any report server licenses.

ReportBridge currently runs report server version 13.1.26, fully managed and maintained by our operations team. All updates, patches, and production deployments are handled by ReportBridge. You do not need to manage any server infrastructure.

All credentials are stored in AWS Secrets Manager (single JSON blob per instance) and a Postgres-authoritative workspace database on Multi-AZ RDS. Passwords are masked as [configured] in all API responses across 13 sensitive fields. The Lambda requires only 4 bootstrap environment variables and loads all other configuration at runtime. Multi-organization deployments store per-org config with instance_id isolation and Row-Level Security on all tenant tables.

ReportBridge's architecture has been reviewed against the AWS Well-Architected Framework across multiple review rounds, with all CRITICAL and HIGH findings resolved. The platform has 1,900+ automated tests, including dedicated security and tenant-isolation suites covering SSRF prevention, SQL injection, credential masking, auth rate limiting, and cross-tenant write prevention. Every code change runs through CI with build verification, unit tests, and live infrastructure smoke tests.

Tenant isolation is enforced at three layers: (1) API key layer — each tenant receives a unique HMAC-derived API key that is cryptographically bound to their instance, (2) application layer — every workspace query includes explicit instance_id filtering enforced server-side regardless of what the client sends, and (3) database layer — PostgreSQL Row-Level Security policies on all 8 tenant tables prevent cross-tenant reads even if a query omits the WHERE clause. A 16-test E2E isolation suite validates these controls automatically.

All communication uses HTTPS/TLS 1.3 throughout — between Domo and the Lambda API Gateway, between Lambda and PostgreSQL, and between Lambda and the report server behind the ALB with auto-renewing ACM certificates. The Lambda API bridge uses parameterized queries, DDL/DML blocking, statement allowlists, and read-only transactions to prevent SQL injection. Error responses are sanitized to strip IPs, passwords, connection strings, and tokens.

ReportBridge is a fully managed SaaS subscription available as a standalone web app at report-bridge.com or as Domo ProCode apps (Domo Marketplace coming soon). The Viewer is free. The Admin platform (AI conversion, publishing, management, monitoring, and backups) starts at $499/month after the 30-day free beta trial. All infrastructure and report server licensing costs are included. See the pricing page for details.

No. Your ReportBridge subscription includes all infrastructure: report server hosting, AWS compute, database, load balancing, SSL certificates, monitoring, backups, and report server licensing. The only optional cost is your own AI provider API key (Anthropic Claude or AWS Bedrock) if you use the AI-powered SQL conversion feature.