UDR · HC-01 · Cloud preview · v0.1
Housecarl AuthZ
AuthZ for the hardest problems.
 Operational
Private beta · Q2 2026
housecarl.cloud
Overview Documentation Pricing News Security Open console →
UDR-HC-01 · Authorization, in writing

AuthZ for the
hardest problems.

Policy-as-contract authorization. Multi-tenant. Fine-grained. Audited. CLI-first. Self-hosted or cloud — the security team writes policy in a form that the machine can verify, and the developer integrates once.

p99 < 5ms Decision latency target
∞ MAUs Per tier — pay for calls
100% Decisions audited
I. What you get

The capability set, in writing.

01

Fine-grained, resource-level control

Match access policies to the exact resources they govern. No coarse roles, no wildcards by default — what is permitted is named.

02

Multi-tenant by construction

Tenant isolation is a property of the data model, not an opt-in flag. Customers cannot see each other's policies, users, or resources.

03

CLI-first design

Every operation has a flag. Test, dry-run, diff, and apply policies through housectl — review them in pull requests like any other artifact.

04

Self-hosted or cloud

Operate Housecarl in our cloud, in yours, or on your bare metal. The same binary, the same wire format, the same policy semantics.

05

Single sign-on, in production

Google OAuth today. GitHub and Azure AD ready. JWT-backed sessions, attribute mapping, and role inheritance are first-class concerns.

06

Auditable by default

Every authorization decision is logged with principal, action, resource, and policy reference. Audit log is queryable and exportable.

07

Built-in billing

Subscription management with usage tracking. Monetize a multi-tenant product without writing a billing service first.

08

Engineered to last

Rust on the wire and at rest. PostgreSQL for state. gRPC for the data plane. Nothing exotic; everything explicit.

II. Who it is for

Teams that have outgrown roles & bools.

A

Complex permission models

Multiple teams with different permission structures. Matrix roles with cross-cutting access. Organizations whose access patterns don't fit a flat list of capabilities.

B

Compliance-driven engineering

Policies that mirror regulatory or corporate controls — and an audit trail that demonstrates them.

C

On-premise control

Self-host to maintain compliance with information controls your security team has already deployed.

D

MLS & high-rigor deployments

Multi-level security. Air-gapped sites. Edge and disrupted environments — on the roadmap, not as an afterthought.

Read the docs. Then ask for an account.

Housecarl AuthZ ships in Q2 2026. Cloud and self-hosted editions exist. Private beta is open for serious operators.