holo
THE FOUNDATION
Your data, modeled.
Models, migrations, relationships.
PostgreSQLMySQLSQLite
Explore the ORM
THE BACKEND FRAMEWORK FOR NEXT.JS, NUXT & SVELTEKIT
Build the product.
Skip the plumbing.
A complete backend for Next.js, Nuxt, and SvelteKit.
Keep
your framework. Get your backend together.
AuthIDENTITY
ModelsDATA
SessionsCONTEXT
EventsREACTIONS
QueueBACKGROUND
StorageFILES
CacheFAST PATH
PoliciesPERMISSIONS
MailDELIVERY
ValidationCONTRACTS
RealtimeLIVE STATE
NotificationsCHANNELS
The pieces are familiar. The wiring is your problem.
YOUR APPLICATIONNext.js
WEB LAYERRoutesRenderingDeployment
HOLO BACKEND INSIDE YOUR APP
Typed modelsAuthenticationBackground jobsFile storage
ONE APPLICATIONFrontend freedom. Backend structure.
One click.
A connected backend.
From permission to persistence to background work.
AUTHORIZATION
Permissions belong
Permissions belong
to your domain.
Define an ability once. Reuse the same decision in routes, jobs, and services.
Explore authorizationInspect the real API
server/abilities/publish-post.tsDOCUMENTED API
import { defineAbility, allow, deny }
from '@holo-js/authorization'
export default defineAbility('posts.publish',
context => context.user?.role === 'editor'
? allow()
: deny('Editor access required.')
)
A backend decision.
Not a frontend migration.
Same backend conventions. The route syntax you already know.
app/api/posts/route.ts
import Post from '@/server/models/Post'
export async function GET() {
const posts = await Post
.where('status', 'published')
.latest()
.paginate(15)
return Response.json(posts)
}
Your route. Your rendering. Holo underneath.
Your code stays.
Your infrastructure can change.
One contract. Different drivers.
Explore what each module
does.
@holo-js/storage
Different disks. Same file API.
Store files locally, serve public uploads, or use S3-compatible storage through the same API. Your media library builds on these disks with model collections and conversions.
CONFIG CHANGES
defaultDisk: 'local'
SAME APPLICATION CODE
await Storage.put('avatars/ava.png', file)
const avatar = await Storage.get('avatars/ava.png')
INTERACTIVE ILLUSTRATION
avatar.png → public disk
Storage uses the configured default disk. S3 credentials and disk configuration belong in your environment.
Explore storage →Explore the media library →
@holo-js/db
New database. Same domain.
Start with SQLite, move to PostgreSQL or MySQL. Keep your model calls and portable schema migrations while the configured connection changes.
CONFIG CHANGES
driver: 'sqlite'
SAME MIGRATION
await schema.createTable('posts', table => {
table.id()
table.string('title')
table.timestamps()
})
INTERACTIVE ILLUSTRATION
Portable schema → configured database
Install the chosen driver and configure its connection. Existing data must be migrated separately; database-specific SQL is not portable.
Explore database →
@holo-js/auth
One auth layer. Your choice.
Local login, sessions and API tokens, plus Clerk and WorkOS. Hosted providers sync into your local user model and create a normal Holo session.
API AT A GLANCE
import { user } from '@holo-js/auth'
const currentUser = await user()
INTERACTIVE ILLUSTRATION
Your sign-in → local user → Holo session
Keep identity choice inside one authentication module.
Explore authentication →
@holo-js/realtime
Change data. Update the screen.
Define typed server queries and mutations. When matching Holo database writes commit, live query results refresh in connected browsers.
API AT A GLANCE
query(...) // read typed data
mutation(...) // write typed data
BROWSER ADraft
BROWSER BDraft
INTERACTIVE ILLUSTRATION
Draft → query result
Run the broadcast WebSocket worker to deliver live browser updates.
Explore realtime →
@holo-js/notifications
One event. Every channel.
Define a notification once, then deliver it through email, database and broadcast channels. Queue or delay delivery when your product needs it.
API AT A GLANCE
defineNotification({
via: () => ['email', 'database', 'broadcast'],
// channel-specific builders
})
EmailDatabaseBroadcast
INTERACTIVE ILLUSTRATION
Invoice paid → one notification
Email uses the mail sender. Live broadcast uses the configured transport.
Explore notifications →
@holo-js/mail
Email belongs in your app.
Define a typed email, preview it in the browser, and send it through a configured driver. Add Markdown, attachments or queued delivery.
API AT A GLANCE
await sendMail(welcomeMail({
to: 'ava@example.com', name: 'Ava',
})).using('preview')
INTERACTIVE ILLUSTRATION
Welcome, Ava. Your account is ready.
TO ava@example.com
Welcome, Ava.
Your account is ready.
Open your dashboard →Preview, log and SMTP drivers share the mail delivery contract.
Explore mail →
@holo-js/queue
Change the engine. Keep the job.
Write a typed job once. Run it inline with sync, or dispatch it through database and Redis connections. Attempts, backoff and failed jobs stay explicit.
CONFIG CHANGES
default: 'sync'
SAME APPLICATION CODE
await GenerateReport.dispatch({ reportId })
QueuedProcessingComplete
INTERACTIVE ILLUSTRATION
Report requested → queued
Sync runs inline. Database and Redis need workers; database queues also need their queue-table migration.
Explore queues →A TOOLKIT, NOT A TAKEOVER
A complete backend.
Your combination.
Pick your pieces. Your choices become your starter command.
3 optional modules selected
See your starter command
IDENTITY & TRUST
Identity, handled.
Auth, sessions, and permissions.
Explore identity
WORK BEYOND THE REQUEST
Work, off the request.
Typed jobs. Explicit retries.
Explore background work
FILES, SPEED & CONNECTIONS
Files, wherever you need.
Local and cloud disks. One API.
Explore storageYour next app.
Ready for more.
The stack you chose. One command to start.
YOUR OPTIONAL MODULES
npm create holo-js@latest my-app -- --framework next --database
sqlite --package auth,queue,storage
Node 22.12+ · MIT licensedReview configuration after scaffolding.
Orange modules are included in your app.