zelavis

zelavis is the high-level runtime package for the Zelavis App Platform.

Use it when you want the default platform building blocks wired together through one runtime entry point.

Current role

Today, that mostly means:

dashboard delivery
auth service
database service
storage service when an adapter file store exists
website service
service activation
project and server dashboard surfaces
runtime composition

Main entry point

import { Zelavis } from "zelavis";
import { nodeAdapter } from "zelavis/adapters/node";

const zv = new Zelavis({
  adapter: nodeAdapter(),
});

Treat this as the normal public API.

High-level vs low-level

Prefer these layers in order:

new Zelavis(...) for application/runtime work
scoped packages like @zelavis/server for primitive-level infrastructure

The lower-level zelavis() function still exists, but it now intentionally owns the internal runtime controls such as:

direct services
path and mount overrides

The Zelavis class is the product-facing entrypoint. Built-in services are part of the runtime by default; lower-level route mounting knobs stay on zelavis().

Examples use zv as the short local name for a Zelavis runtime instance.

Default behavior

By default, Zelavis owns one safe namespace under /zelavis and includes dashboard, auth, database, website, and workloads core services.

The dashboard stays mounted under the configured root path, while API services stay grouped under /api/<version>/....

The dashboard root opens Projects. Global surfaces such as Marketplace and Server live outside project URLs, while Zelavis-native project pages live under /zelavis/projects/:projectId/*.

The dashboard is a client of the runtime. Operations shown in the dashboard should also be available through stable runtime capabilities and versioned endpoints so CLI tools, AI agents, scripts, plugins, and external admin clients can perform the same work.

Default dashboard paths include:

/zelavis
/zelavis/marketplace
/zelavis/projects/default
/zelavis/projects/default/marketplace
/zelavis/projects/default/settings
/zelavis/server
/zelavis/server/domains
/zelavis/server/backups
/zelavis/server/logs
/zelavis/projects/default/workloads

Application code can access core service APIs through the runtime instance:

await zv.db.documents.createCollection({ name: "posts" });

const doc = await zv.db.documents.insert({
  collection: "posts",
  data: { title: "Hello" },
});

const account = await zv.auth.accounts.create({
  id: "owner",
  email: "[email protected]",
});

When to use lower-level packages instead

Use scoped packages directly when you need lower-level control over primitives, adapters, or tests:

@zelavis/server
@zelavis/db
@zelavis/auth

The lower-level zelavis() function still exists for internal runtime composition, but the main public application-facing entry point is the Zelavis class plus a runtime adapter.

Available runtime adapters:

zelavis/adapters/node
zelavis/adapters/bun

Deno is a planned runtime target.

Serverless function platforms are not Zelavis runtime targets. Managed providers may appear through optional plugins for user websites, storage, DNS, CDN, email, or other provider adapters.

Framework utilities (small wrappers around zv.fetch) live at:

zelavis/express, zelavis/hono, zelavis/fastify, zelavis/h3, zelavis/elysia
zelavis/nextjs/pages (Next.js Pages Router)
zelavis/node (standalone Node HTTP server)