Security
CSRF tokens, rate limits, and CORS policies. The hooks ship with the framework; the runtime that enforces them doesn't.
Appearance
Holo-JS
Pick your backend.
Modular backend pieces for Nuxt, Next.js, and SvelteKit. Install what you need. Skip the rest.
What you pick is what you ship.
Database@holo-js/db
Auth@holo-js/auth
Session@holo-js/session
Authorization@holo-js/authorization
Security@holo-js/security
Queue@holo-js/queue
Cache@holo-js/cache
Storage@holo-js/storage
Events@holo-js/events
Broadcast@holo-js/broadcast
Realtime@holo-js/realtime
Forms@holo-js/forms
Validation@holo-js/validation
Mail@holo-js/mail
Notifications@holo-js/notifications
Media@holo-js/media
Explore all featuresStorage@holo-js/storage
Queue@holo-js/queue
Database@holo-js/db
Your stackWhy Holo-JS
What your framework doesn't ship.
Routing and rendering come in the box. The rest of a production backend doesn't.
Data
Frameworks don't pick a database, an ORM, or a migration story. Every app wires it from scratch.
Auth and sessions
Sessions, tokens, password reset, social login. The route is yours. The system behind it isn't shipped.
Background jobs
Queues, workers, and retry logic live outside the request lifecycle. Frameworks don't ship them.
Files and uploads
Local disks in dev, cloud buckets in prod. The bridge between the two is your problem.
Realtime
Channels, listeners, presence, and broadcasts. Every app reinvents the wiring on top of the framework.
Features
Pick the layers your app needs.
No bundled bloat. No defaults you didn't choose. Install one module, install all, or swap drivers. The runtime stays the same.
Database
@holo-js/dbTyped query builder, models, migrations, and seeders.
Auth
@holo-js/authSessions, providers, tokens, and social login.
Session
@holo-js/sessionCookie sessions, stores, guards, and framework-safe session access.
Authorization
@holo-js/authorizationPolicies, abilities, gates, and typed permission checks.
Security
@holo-js/securityCSRF, CORS, rate limits, and request protection primitives.
Queue
@holo-js/queueBackground jobs with retries and failed-job tracking.
Cache
@holo-js/cacheDrivers, locks, and query-level caching.
Storage
@holo-js/storageFile storage across local and cloud drivers.
Events
@holo-js/eventsListeners, queued listeners, and after-commit hooks.
Broadcast
@holo-js/broadcastRealtime channels, auth routes, and Flux helpers.
Realtime
@holo-js/realtimeTyped queries, mutations, subscriptions, and live state wiring.
Forms
@holo-js/formsValidated server actions with framework adapters.
Validation
@holo-js/validationSchema contracts, typed parsing, and reusable validation surfaces.
@holo-js/mailMailables, fluent sending, previews, and delivery contracts.
Notifications
@holo-js/notificationsNotification channels, dispatch helpers, and delivery routing.
Media
@holo-js/mediaMedia collections, conversions, and model file attachments.
Beside, not instead of
Holo-JS works with your framework, not around it.
Keep the routing, rendering, and conventions you already use. Holo-JS adds typed backend services with first-class adapters for each host.
- NuxtServer routes, Nitro handlers, and auto-imports keep working. Holo-JS plugs into the Nitro lifecycle.
- Next.jsApp Router, route handlers, and server actions stay the source of truth. Holo-JS adds the backend layer beneath them.
- SvelteKitEndpoints and form actions are unchanged. Holo-JS provides the runtime services they call into.