What is HVT?

HVT is the account system behind your product. Your team configures the boundary once, and your app uses that boundary for signup, login, social auth, tokens, audit logs, and webhooks.

What HVT does

HVT is open-source authentication infrastructure. Instead of building your own account system from scratch, you create an organisation, create a project for each app or environment, issue an API key for that project, and let HVT handle the auth flow for that app.

Platform isolation

HVT has two separate user types. Platform users are developers who manage HVT via the dashboard. Runtime users are end users of apps built on HVT. Runtime users cannot access the dashboard or any control plane endpoint. This is enforced at the backend.

Read Platform users and runtime users before you wire up runtime signup or login.

In practice, that means HVT can register users, sign them in, refresh tokens, run social login, emit audit events, and send webhooks while keeping the organisation and project context attached to every runtime action.

If you want the shortest plain-English explanation, it is this: HVT runs the login system for your app and keeps the business boundary around that app clear.

What teams do first

  1. Your team creates an organisation in HVT.
  2. Your team creates a project for the app or environment you want to protect.
  3. Your team issues an API key for that project.
  4. Your app sends signup, login, social auth, or token refresh requests to HVT using that project context.
  5. HVT returns users and tokens, and records what happened through audit events and webhooks.

Control plane and runtime

HVT is easiest to understand when you split it into two halves.

Control plane

Your team signs in here.

You create organisations, create projects, issue API keys, invite teammates, and configure social providers.

Runtime plane

Your app uses this part.

Your users sign up, log in, use social auth, refresh tokens, trigger webhooks, and generate audit events through this runtime surface.

Self-host or use hvts.app

Self-host HVT when

You want full code ownership, you need to audit how auth works, or you want to run the platform on your own infrastructure.

Use hvts.app when

You want the same organisation, project, and runtime model, but you do not want to operate the infrastructure yourself.