Choose a starting project
Choose the smallest example that demonstrates your application's boundary. First get its login and protected request working; then replace the example's data and storage with your product's implementation.
Run a public package example
The package quickstart includes the clone, install, and run commands for a complete local Hono application. It needs Deno 2 and Git, and does not need a hosted account, database, or email service.
| Your project | Example or guide |
|---|---|
| Hono app that owns its authentication | Local Hono application |
| Hono app connecting to a separate issuer | Hono with external auth |
| Server-rendered React app with delegated sign-in | Juniper with external auth |
| An API without a frontend | Hono API service |
| A new React app that runs its own authentication | Juniper template or React Router template |
| An existing app using managed identity | Use Udibo |
The examples are development fixtures. In-memory stores reset on restart and demo credentials are public. Follow the example's instructions and the deployment guide before using it as the basis of a production app.
Explore the service walkthroughs
These guides explain how to assemble a product on the hosted service:
| Product shape | What you will learn |
|---|---|
| B2B SaaS | Organizations, a protected project list, organization-specific actions, and verified webhooks |
| Consumer app | Hosted account pages, profile claims, verified email, and records belonging to one user |
| Client portal | Per-document access, organization grants, and checks for a list of resources |
These service templates do not yet have standalone public distributions. Read the walkthroughs as implementation guides. Use a public package example for a runnable starting point, or coordinate access to the service templates through your beta setup. A hosted account alone does not grant repository access.
If you have beta template access
Complete application registration first. The templates expect these server-side settings:
| Variable | Value |
|---|---|
UDIBO_ISSUER | Your tenant's trusted issuer origin |
APP_ORIGIN | This application's origin; its registered callback is {APP_ORIGIN}/auth/callback |
UDIBO_CLIENT_ID | The confidential application registration's ID |
UDIBO_CLIENT_SECRET | Its one-time client secret |
UDIBO_WEBHOOK_SECRET | B2B SaaS only: the secret for the endpoint at {APP_ORIGIN}/webhooks/udibo |
In the provided development checkout, run deno task dev from the selected
template directory after configuring its environment. The default development
ports are 8007 for B2B SaaS, 8008 for the consumer app, and 8009 for the client
portal. Register the callback for the origin you actually run.
The B2B and portal walkthroughs require the relevant organization, permission, and resource setup too. Complete those steps through the supported administrator workflow; do not embed an administrator's session in your application.
Make the example your own
Keep the authentication boundary while replacing the demonstration data. Implement durable sessions and application storage, preserve resource ownership checks, configure production callbacks and secrets, and test both successful and refused requests. A frontend route guard does not protect the API.
Next: Connect your first application, then prepare for production.
Last verified 2026-09-06.