MeshERP SQL Connectors
Point your reporting tools at the archive, not at production
Read-only SQL and OData over the retained copy of your ERP data. Whatever speaks PostgreSQL or OData connects to it: Power BI, Excel, Looker Studio, a scheduled job, your own service.
What it does
One connection string, and the tools you already own
The archive is a database you can query, so nothing has to be exported, reshaped or scheduled into a warehouse first.
- Read-only SQL over the retained copyA read-only PostgreSQL connection into a vendor-hosted isolated tenant database, with customer administrative read-only SQL access. Real tables and columns, not an export you have to reshape first.
- OData for the tools that want itTools that expect an OData feed connect that way instead, over the same retained data and the same permissions.
- Production stays out of itQueries run against your archive. Your ERP does not carry the load, and nothing on this path writes back to it.
Accounts and roles
Unlimited accounts, each with its own permissions
Give the finance team one login, the BI service another, and a contractor a third that reaches only what you scoped for it. Unlimited here means accounts and roles, not query volume.
Administrative
Read-only access to the replicated fields the account is authorized for. For administrators, developers and approved service accounts.
Filtered
Views you define, with selected columns hidden, masked or omitted. For BI tools and lower-trust operators.
Scoped
Selected objects, rows, records and fields. For departments, projects and narrow integrations.
Database roles and policies enforce the difference between profiles, and a separate restricted API covers integrations that do not need SQL. The trust page has the architecture.
In practice
Where the connection earns its place
Four jobs that stop being a project once the data answers a query.
A dashboard that never touches production.
Point Power BI, Looker Studio or Tableau at the archive instead of the ERP.
A spreadsheet that refreshes itself.
Excel connects over OData and pulls the columns it needs on a schedule you set.
An integration that only ever reads.
Give it a service account scoped to the objects it needs, and nothing else.
History in your own queries.
Supported historical data sits in the same connection as the current copy.
The archive and its history are the product. MeshHistory and MeshWatch are the services a subscription turns on, and this is how the tools you already own reach them.
Subscriptions
An add-on, on whichever subscription needs it
Read-only SQL access attaches to a single subscription, so you add it where the querying happens and leave the others alone.
Read-only SQL access
An add-on on any subscription. Unlimited SQL accounts and service accounts, each with its own roles and permissions.
Which ERP should we connect first?
NetSuite is first. Tell us what you run and vote for the connector you need next. MeshERP is in pre-launch, so nothing here is purchasable yet.