Under the hood
How it’s built.
You’re trusting us with your company’s operating data, so here is exactly how the platform works — the architecture, the storage, the backups, and what we built on. Every claim on this site should be checkable; this page is where you check it.
The isolation model
One building. Separate vaults.
Most SaaS puts every customer’s rows in shared tables and separates them with query filters. We don’t. Each workspace is a physically separate PostgreSQL database, reachable only at its own subdomain.
your-org.everjust.app
acme-co.everjust.app
north-supply.everjust.app
A request to your-org.everjust.app can only ever reach the your-org database — the server is configured so no other database is visible to it. Cross-tenant queries aren’t forbidden by policy; they’re impossible by wiring.
Your data is a database you could walk away with
Export records from any list view, download files in bulk, or ask us for the full database. It's yours — LGPL open-source underneath means no proprietary format holds it hostage.
Backups on a rolling schedule
Every tenant database is backed up on a rolling schedule and before every platform update. No backup add-on, no storage tier.
TLS everywhere, secrets server-side
Wildcard TLS covers every workspace. Payment details live at Stripe and never touch our servers. Passwords are salted hashes.
Your brand, not ours
Login page, emails, receipts, mobile app icon — your customers and staff see your name. The platform doesn't advertise itself anywhere in your workspace.
The foundation
Built on open source, extended where it counts.
The core is a mature LGPL-3 open-source business suite with two decades of development behind it. We didn’t rebuild accounting or inventory from scratch; we built the parts that didn’t exist:
The multi-tenant platform
Database-per-customer isolation, automated two-minute provisioning, subdomain routing, per-tenant backups — the machinery that turns one engine into private workspaces.
A native mail platform
A built-in webmail client with custom-domain sending and receiving, bounce and complaint suppression, and per-mailbox signatures — not a relay checkbox.
Embedded telephony
Calls and texts are logged on the customer record. Provider integrations carry them.
White-label, everywhere
A brand system that sweeps every surface — login, emails, receipts, portal, mobile icon — and re-applies itself on every update.
Agent access over MCP
A secure, audited MCP endpoint per workspace so customers' AI tools can operate their own data. See Connect your AI.
Personalized onboarding
We set your starting apps, and your logo and name are applied before you first sign in.
Why not name the upstream project? Its trademark isn’t ours to market with, and your workspace carries your brand, not theirs or ours. The licensing is LGPL-3 and our extensions are LGPL-3-compatible.
The honest parts
Limits we’d rather you hear from us.
Platform updates cause brief maintenance windows
We batch changes and deploy in quiet hours; during a deploy, workspaces can be unreachable for a few minutes. We verify every workspace afterward.
We're a small team
That's why support is a person answering company@everjust.co and why this page exists — depth of disclosure is our substitute for a wall of logos. Your exit is always open: your data is one exportable database.
Custom-domain email is a guided setup
Sending from you@yourcompany.com requires DNS verification, and today we do that setup with you rather than fully self-serve. It's real, it works, and it takes a conversation — see Mail.
Next step
Ask us the hard questions live.
Thirty minutes on a real workspace — architecture questions welcome.