OQ — X00 · Enterprise
Reserved capacity so your queries never queue behind someone else's, programs decoded to your specification, and results that carry enough provenance to survive an audit.
- Reserved capacity
- Yes
- Custom IDLs
- Yes
- SSO & audit logs
- Yes
- Support
- Named engineer
The SQL surface is the same one everybody gets. What enterprise changes is capacity, coverage, control and the contract around them.
Reserved engines
Dedicated capacity so a large export from another tenant cannot slow your morning refresh.
Custom decoding
Programs outside the bundled catalog decoded to the same typed-table convention, including private or pre-launch programs.
SSO and audit logs
Directory-backed access with a full record of who ran what, when, and against which catalog hash.
Higher limits
Raised submission and execution ceilings where the workload genuinely needs them.
Private datasets
Tables visible only to your organisation, resolved through the same catalog validation.
Named support
A support engineer who knows your workload, plus an SLA on response and uptime.
Scope the workload
Which programs, which queries, what volume, and what has to be provable. Usually one call and a shared document.
Decode what is missing
Any program outside the bundled catalog is decoded from its IDL into the same typed-table convention.
Provision capacity
Reserved capacity sized to the workload, with SSO wired to your directory.
Port and verify
We port a query you already trust and compare the numbers against your current source before you cut over.
Where does our data live?
OnchainQueries is read-only over typed Solana event tables — public chain data. Your queries, results and access logs are yours; results expire after 24 hours by default and can be retained differently under contract.
Can you decode a program that is not public yet?
Yes. Custom decoding works from the IDL, so a program does not need to be public or even deployed to mainnet for its tables to exist in your private catalog.
How do we audit a number months later?
Every result manifest records the physical tables read, the catalog hash and the high-watermark slot, plus a SHA-256 per part. Keep the manifest and you can prove what the number was computed from.
What is the security posture?
The platform is read-only by construction: no data or schema modification, no system tables, no external table functions, and credentials never leave the execution layer. Arrow Flight upload and exchange methods are disabled outright.
We will tell you honestly whether OnchainQueries is the right tool for it.