Open Source · AI-Customizable · Self-Hosted

The open-source foundation for AI products

Start with multi-tenant auth, billing, payments, credits, and an admin console. Use AI to shape the rest around your product—not your infrastructure.

Star on GitHubGet StartedLive Demo
terminal
$git clone https://github.com/timzaak/herald.git
$cd herald
$uv run scripts/demo-start.py
→ Starting PostgreSQL + Redis ...
✓ Database migrated
✓ Multi-tenant auth (RBAC, OAuth, TOTP)
✓ Subscription billing (Stripe, Creem)
✓ Admin console @ http://localhost:3000
→ Your AI product infrastructure is ready. Build what makes it unique.

The infrastructure around your AI product

Herald handles the shared product foundation so your team can spend its AI iterations on the logic customers actually pay for.

Multi-Tenant Auth

Isolated Realms, each with its own users, roles, and OAuth providers.

  • Realm tenant isolation
  • OAuth 2.0 providers
  • TOTP & passkeys

RBAC & Client Apps

Fine-grained roles per Realm, plus app registration with scoped credentials.

  • Per-Realm role permissions
  • Client App registration
  • Third-party API integration

Billing & Payments

Subscription plans and one-time purchases, mapped to providers and Client Apps.

  • Plans & pricing tiers
  • Stripe & Creem
  • Invoices & entitlements

Points & Credits

Multi-pool credit balances that meter product usage.

  • Multi-pool consumption
  • Distribution & quota rules
  • Per-user transaction history

Consent & Compliance

Versioned Terms and Privacy Policies per Realm, hosted or external.

  • Version-bound re-consent
  • Hosted or external pages
  • Auditable account deletion

MCP Server for AI Agents

Agents query your realm through permission-gated tools, not hand-written REST calls.

  • Nine read-only tools
  • Browser OAuth + per-user RBAC
  • Streamable HTTP at /mcp/{realmId}

From repository to AI product in three steps

Deploy the foundation. Shape it with AI. Build your product logic.

01

Deploy with Docker

Clone the repo, point your domain, and run dev-start.py. PostgreSQL, Redis, Caddy (with auto-TLS), and the Herald app start together on one machine.

02

Shape It with AI

Use AI-assisted development to adapt the open codebase, product flows, branding, roles, and integrations to your market.

03

Build Your Product Logic

Connect your application through Herald's APIs and OAuth 2.0 endpoints. Keep iterating on the experience that makes your AI product worth paying for.

Why AI startup teams choose Herald

Go beyond authentication with billing, payments, credits, and product infrastructure in one AI-customizable, self-hosted system.

HeraldAuth0SupabaseKeycloak
Multi-tenant auth
Included
Enterprise onlyManual setupIncluded
Subscription billing
Built-in
———
Points & credits
Built-in
———
Self-hosted
Yes
Cloud onlyYesYes
Open source
Apache-2.0
NoPartialApache-2.0

Frequently asked questions

Everything you need to know about Herald.

What is Herald?
Herald is an open-source, self-hosted foundation for AI products. It gives startup teams multi-tenant auth, RBAC, billing, payments, credits, and an admin console in one codebase they can keep adapting with AI.
How does Herald help me build an AI product faster?
Instead of spending early iterations stitching together auth, payment webhooks, entitlements, credits, and admin tools, you start with those systems connected. Your team can use AI-assisted development on the open codebase and focus on product logic.
How is Herald different from an auth provider?
Herald is more than an authentication layer. It connects identity to subscriptions, one-time payments, entitlements, credits, invoices, and tenant administration, so paid access and product usage share one foundation.
What does multi-tenant mean in Herald?
Multi-tenant means Herald organizes your users and data into isolated Realms. Each Realm is a separate tenant with its own users, OAuth providers, Client Apps, and billing plans. Data between Realms is fully isolated.
How do I deploy Herald?
Herald deploys with Docker. You need a Linux server (Ubuntu 22.04+, 2GB RAM), Docker Engine 24+, and a domain. Four containers run together: the Herald app, PostgreSQL, Redis, and Caddy.
What payment providers does Herald support?
Herald supports Stripe and Creem for subscription payments. You can create subscription plans with different pricing tiers, map plans to specific payment providers, and assign plans to Client Apps.
What tech stack does Herald use?
Herald uses Rust (Axum framework) for the backend API and React with TypeScript for the frontend. Data is stored in PostgreSQL with SeaORM, and Redis handles sessions and caching.
Is Herald free and open source?
Yes. Herald is released under the Apache-2.0 license. You can use, modify, and distribute it freely, including for commercial projects. There are no usage limits and no per-user fees.
Can I get help evaluating or deploying Herald?
Yes. Email zsy.evan@gmail.com and tell us about your product — we can help with deployment, payment-provider setup, and architecture questions. Bugs and feature requests can go to the GitHub issue tracker.

Build the AI product users pay for

Start with the open infrastructure around your product. Use AI to customize it, then focus every iteration on what makes your product unique.

Star on GitHubGet Started

Questions, or building something with Herald? Email us: zsy.evan@gmail.com