Security & tenancy

Isolation by design, not by afterthought.

Security in Gitira starts at the data seam. Every request carries a tenant context, and data access is gated on it — so one org can never read another org’s work.

Tenant isolation

Every customer is provisioned an isolated org. Data access runs through a mandatory tenant-context seam — the boundary is enforced at the core, and verified by automated cross-org tests.

Least-privilege by default

—Deploys are brokered through connectors — no standing personal credentials in the release path.
—Secrets are encrypted at rest and never returned to the client.
—Access is scoped to the verified principal, not self-asserted headers.

Operational safety

Crashes are treated as telemetry: durable records, automatic recovery, and a health surface — so incidents are visible and reviewable, not silent.

Reporting a vulnerability

Found something? Email security@gitira.com. We appreciate responsible disclosure and will acknowledge your report.