Every company has a values page. Most are written by marketing, ignored by engineering, and have nothing to do with the product. Ours isn’t. These five values shape every decision we make about Vloud — what we build, what we refuse to build, and how we ship.
1 — Your data stays on your server
The line is bright. Vloud is a single binary that runs on your host. Application payloads, user records, log contents, file uploads — none of it phones home. Ever. The only outbound call is a heartbeat every six hours to validate your license; if that fails, the engine operates in a 72-hour grace window then enters read-only mode. We’ve turned down feature requests that would require us to break this.
2 — Audit is public, not promised
When we issue a license, sign an update, or modify your engine’s config remotely, that event lands in a Merkle tree you can read. No “trust us, we’d never.” Inspect the chain, compare it against what your engine reports locally, and you have proof. We treat transparency as engineering, not marketing copy.
3 — Same input, same answer
Indexing, retrieval, and security scans are deterministic. Same input, same output, every time. We don’t hide non-determinism behind “AI magic.” When the AI Doctor explains a deployment failure, it walks you through evidence: log lines, file diffs, env values. You can disagree with its conclusion — and check the reasoning.
4 — Citations or it didn’t happen
Every claim our security engine makes is traceable: which scanner, which signature, which file path, which line. Every alert links to the underlying event. No black-box “we noticed something.” If we can’t tell you exactly what we found, we don’t show you a warning.
5 — Calm by default
Modern monitoring tools are built for outage drama. Vloud is built for calm. Real-time alerts are off by default. The dashboard’s first job is to show you what’s normal, not what’s on fire. When we notify you, we mean it. The signal-to-noise ratio is the product.
These five aren’t aspirational. They’re the constraints we work within. If a feature would compromise any of them — even when a customer asks — it doesn’t ship. Read the rest of this blog for the specific decisions that come from each one.