Company
Built for the institutions everyone else asks to compromise
DataQube started from a simple observation: the organizations with the most valuable data - banks, insurers, asset managers - are precisely the ones that can't use cloud AI assistants. The answer isn't a worse assistant with a compliance sticker. It's a better one that runs where the data lives.
01Principles
How we build
Six rules that show up in the product, the codebase, and the contract.
Nothing silently mutates
Threads, decks, memories, permissions - changes only ever add, with the full history visible. If something changed, you can see what, when, and why. This is the design rule the whole product hangs from.
Do the correct thing
Enterprise systems demand correctness over convenience. We choose the harder-but-correct design - keeping visible history instead of quiet cleanup, exact rules instead of special cases - because our customers' auditors will read the result.
The answer carries its evidence
An insight without provenance is an opinion. Every number DataQube produces is traceable to the query, the rows, and the file section behind it - by construction, not by discipline.
Guest in the customer's house
We deploy into infrastructure we don't control and shouldn't. Nothing calls home, nothing is tracked, and no data leaves unless you move it. The customer's perimeter is the law of physics we design within.
Security is never an upsell
Every tier ships the same architecture: isolation, authorization, audit, encryption. We don't sell trust as an upgrade, because the customers we serve can't buy halfway.
Tribal knowledge belongs to the institution
The conventions in analysts' heads are the institution's most expensive asset and its least protected. We build the place where that knowledge becomes durable, validated, and shared.
02Working with us
Small team, deep stack
We're engineers who have lived inside regulated data estates - Rust on the backend, a security model auditors compliment, and a product opinionated enough to say no. If that sounds like home, we'd like to hear from you.
We hire deliberately
No open-roles board right now - but we read every thoughtful note. Tell us what you've built and what you'd fix about DataQube after a week.
careers@data-qube.com
See your data answer questions - without leaving your infrastructure
Thirty minutes with an engineer: live product, deployment options, and your security team's questions answered by someone who wrote the code.