Transparency & trust

How alexandr is built

• Signed releases. Every desktop release is code-signed, and Mac builds are notarized by Apple, so you can verify the app you run is the one we shipped. Updates are delivered automatically.
• One runtime, everywhere. The same runtime powers alexandr on your computer, in our cloud and on premises. There's no hidden "cloud edition" that behaves differently.
• Clear boundaries. The parts of alexandr — the desktop apps, the runtime and our cloud — communicate only through defined, typed contracts. That makes it possible to reason about exactly what data moves where.

How alexandr is run

• Isolation by default. Each cloud workspace runs in its own isolated runtime with its own storage.
• Secrets stay secret. Model provider keys and workspace secrets are stored encrypted and are never exposed to the apps running in a workspace.
• Visible usage. AI usage is metered and shown to you, so you always know what your workspace is spending and on which models.
• Public status. We operate a status page for alexandr's cloud services, and we'll report incidents there honestly — including what went wrong and what we changed.

What we'll publish

As alexandr grows, we commit to publishing:

• Which model providers alexandr sends data to, and under what terms.
• Write-ups of significant incidents that affected your data or availability.
• Any change to our commitments, before it takes effect.

A small team, honestly

We're a small company. We don't yet hold formal security certifications, and we won't pretend otherwise. What we can promise is care, candour, and a system designed from the start to keep your data contained. As our customers' needs grow, so will our assurances — and we'll announce each one here.