Infrastructure you don't have to take our word for.
Tessarac is a small engineering-led company. We started by asking why so much of the software running a business can't be inspected by the people paying for it — so we build ours to be. Two products so far, one standard applied to both.
Why we exist
We got tired of infrastructure you have to take on faith.
Most vendors ask you to trust a dashboard, trust a savings claim, trust that an audit log wasn't edited after the fact. We think that's backwards for anything load-bearing — cost, identity, secrets, access. So we started a company built around the opposite default: show the math, keep the evidence, and let the people paying for it check our work.
- We started with the invoice, because it's the easiest number to verify — you already have it.
- Security is next, because “trust us” is even less acceptable there than it is for a cloud bill.
- We're small on purpose — everyone here can explain, in detail, how the system actually behaves.
- If we ever ask you to trust a number instead of showing you the math, that's a bug — tell us.
How we build
A small set of engineering opinions we apply to every commit, every release, every deployment.
Evidence over assertions
If we say something about our own systems — uptime, cost, who touched what — there's a record behind it that can be checked, internally and by customers. We treat ‘trust me’ as a design smell.
Your data leaves in the box it arrived in
No proprietary export format, no log you can't read without us. If we're holding something for you, you can take it back out — designed in on day one, not bolted on when a customer asks.
One codebase, wherever you run it
Hosted, in your own cluster, or fully air-gapped — it's the same image and the same behavior. We don't maintain a lesser fork for self-hosted customers; the hardening around it differs, the software doesn't.
A small team, one standard
We'd rather stay small and hold every release to the same bar than grow headcount and let the bar slip somewhere nobody's watching. Correctness and simplicity aren't a phase we plan to grow out of.
How we do business
We'd rather earn the renewal than win the contract.
We don't do multi-year lock-in, sales-driven feature gating, or pricing that only makes sense with a discount attached. If something we build stops earning its place in your stack, you should be able to walk away from it without an unwind project.
- No multi-year lock-in — you can leave on short notice, and we design exports so leaving is actually possible.
- Pricing tied to value delivered wherever we can manage it, not seat counts or arbitrary usage tiers.
- You talk to the people who build the product, not a tiered support queue.
- Self-hosted and air-gapped deployments are first-class, not a compliance checkbox added later.
Talk to the people building it.
We're a small team, so a question to us reaches an engineer, not a ticket queue. Whether you want to see what we've built or help us build the next thing, both roads start in the same place.