@bworlds/launchkit

Monitoring, error capture, and access gating SDK for AI-built apps. Drop-in integration for Lovable, Bolt, and Base44.

Available on npm: @bworlds/launchkit

Features

• Heartbeat monitoring: automatic uptime tracking, sends a pulse every 5 minutes
• Error capture: catches uncaught errors, unhandled rejections, failed network requests, and console errors; batches and forwards them with readable messages for any thrown value
• Access gating: token-based session validation with redirect to a hosted access page
• Trust badge widget: optional floating "Runs on BWORLDS" pill, toggled from the BWORLDS dashboard (no consumer-side flag)
• Zero config: works with a single buildSlug, no API key required. All settings are managed remotely from the BWORLDS dashboard.
• Lightweight: works in any browser environment
• CDN-ready: use via npm or a <script> tag from unpkg

Install

npm install @bworlds/launchkit

Quick Start

import { init } from '@bworlds/launchkit';

// ── 1. Initialize once (app entry point) ─────────────────
const launchkit = init({ buildSlug: 'my-app' });
// Activates heartbeat monitoring and error tracking automatically.

// ── 2. Gate any protected page ────────────────────────────
const session = await launchkit.check();
if (!session.valid) redirect(launchkit.getGateUrl());
// Redirects unauthenticated users to the BWORLDS access page.

// session.email, session.accessType are available when valid

Replace my-app with your build slug from the BWORLDS dashboard.

Local development against a BWorlds dev stack

When developing a consumer app against a locally-running BWorlds stack (or a PR preview), override the two hosted defaults via config. Both options are drop-in — the built-in gate overlay and redirect keep working, they just point at your local instance.

init({
  buildSlug: 'my-app',
  apiEndpoint: 'http://localhost:3941', // telemetry + token validation
  gateOrigin: 'http://localhost:3939',  // /access/:slug redirect target
});

The SDK scopes all telemetry to the build's registered URL origin. During local development your app runs on localhost, which won't match. Pass dev: true to bypass the origin check:

init({
  buildSlug: 'my-app',
  apiEndpoint: 'http://localhost:3941', // telemetry + token validation
  gateOrigin: 'http://localhost:3939',  // /access/:slug redirect target
  dev: true,                            // bypass origin-scope guard
});

In practice both should be driven from env vars so production falls back to the hosted defaults (undefined → SDK default):

init({
  buildSlug: process.env.NEXT_PUBLIC_BWORLDS_BUILD_SLUG || 'my-prod-slug',
  apiEndpoint: process.env.NEXT_PUBLIC_BWORLDS_API_ENDPOINT || undefined,
  gateOrigin: process.env.NEXT_PUBLIC_BWORLDS_ORIGIN || undefined,
  dev: process.env.NODE_ENV === 'development',
});

Leave the env vars unset in production and the behavior matches the hosted BWorlds exactly. Do not ship dev: true in production — it bypasses the origin guard entirely.

Legacy workaround (pre-1.5.0)

If you're stuck on @bworlds/launchkit < 1.5.0 (no gateOrigin support), disable the built-in gate and redirect manually — at the cost of losing the "Verifying access..." overlay:

const launchkit = init({ buildSlug: 'my-app', apiEndpoint: 'http://localhost:3941', gate: false });

launchkit.check().then((r) => {
  if (!r.valid) window.location.href = `http://localhost:3939/access/my-app`;
}).catch(() => {});

Upgrade to 1.5.0+ to drop the workaround.

Lovable / Bolt / Base44

Paste the snippet above directly into your AI builder as a prompt. The AI will handle the integration.

CDN (no bundler)

<script src="https://unpkg.com/@bworlds/launchkit"></script>
<script>
  BWorldsLaunchKit.init({ buildSlug: 'my-app' });
</script>

How it works

All behavior is configured remotely from the BWORLDS dashboard. The SDK fetches its configuration at startup, no client-side options needed beyond buildSlug.

All requests are write-only and identified by buildSlug. No API key required.

License

MIT