Cloud|

Standalone development

Develop an independent application against the published Cloud package.

2 min read Updated 2026-08-12 #development#standalone#npm

A standalone application depends on @k2b/cloud from npm.

It owns its repository, version, image, and release cycle. It connects to a running Cloud deployment at runtime.

This is the default development shape for third-party applications. Start with Build your first application for the complete package, TypeScript, declaration, and route setup; this page explains how that same app joins a real Cloud environment.

Run the application directly

The development preload configures Solid SSR and watches the application stylesheet:

bash
APP_ID=inventory \
APP_DIR=. \
bun run --preload=node_modules/@k2b/cloud/scripts/preload.ts \
src/index.ts

APP_DIR is the directory containing src/.

Provide the shared platform

A standalone application still needs:

  • the gateway;
  • Core;
  • Postgres;
  • Valkey;
  • any optional service used by the application.

Core serves the shared global stylesheet, fonts, icon font, and branding assets. The application serves its own files below /public/<app-id>/.

Running the application process alone is not a complete browser environment. Direct startup is useful for health checks and application-owned route tests. Use a development Cloud deployment when testing gateway routing, login, shared styles, Settings, or another platform service.

Use published dependencies only

Import only paths exported by @k2b/cloud.

Do not rely on monorepo aliases or import another application package. A standalone build cannot resolve them.

Keep migrations, settings, routes, and static assets inside the application repository.

Verify against the target release

Before release:

bash
bun install --frozen-lockfile
bun run typecheck
bun test

Build the same package version used in production. Test registration, login, one authenticated route, one mutation, and graceful shutdown against the target Cloud deployment.

Treat the target Cloud release and the app's @k2b/cloud dependency as one compatibility decision. Upgrade deliberately, rebuild the image, and repeat the boundary tests before changing production.

See Build and deploy for the production bundle.

Connect a coding agent

The Cloud skill provides compact working instructions. MCP supplies exact current documentation when details matter.

CLI command
bunx skills add https://docs.example.com

This command installs the working instructions published by this website in the selected coding agent.

For exact, current details, also connect the MCP server through one of the agent tabs.

Installation uses the open-source Vercel Skills CLI.

The skill and MCP complement each other: the skill describes workflows, while MCP supplies current documentation.