Use one service

Every Vibiz service works on its own. The app doesn't have to be deployed on Vibiz: it can run on another host, be a plain HTML site, a mobile app's backend, a cron job or a script. A project is just the services you pick, and none of them needs hosting.

#Three steps

1. Create a project with only what you need. vibiz init <name> --resources <one> (MCP: vibiz_create_project { name, resources: ["auth"] }). Payments, files, web data, social, company and connectors need no resource: --resources none (or naming them, --resources payments, makes the same empty project).
2. Add the app's domain as running elsewhere: vibiz domains add app.example.com --elsewhere. From an agent key, analytics counts it at once and sign-in trusts it once its TXT record (trust_record, _vibiz.app.example.com) is in and vibiz domains verify app.example.com finds it, or the owner confirms it in the console. Sign-in trusts it, analytics counts visits from it, and payment events may be sent to it. Not needed for a script or a server with no web address.
3. Give the app its key. One secret, VIBIZ_APP_KEY, reaches everything the project has: an owner copies it from the console and puts it in the host. An agent hands them the link that opens it ready to copy (app_key_console_url from vibiz_project_env), never directions. The app loads the rest at boot:

import { vibiz } from '@vibiz/app';
await vibiz.loadEnv(); // DATABASE_URL, VIBIZ_AUTH_*, VIBIZ_WEBHOOK_SECRET… into process.env

Any language: npx @vibiz/cli run -- <start command>. A build step or CI: npx @vibiz/cli env pull --format dotenv -o .env.production. A connected host (vibiz hosts add <host> <app>) gets the values written for it instead. For local work, vibiz dev writes the development copy (its own key, no production data) to .env.development.local.

#Per service

Without the package, every call above is an HTTP route under /v1/app with Authorization: Bearer $VIBIZ_APP_KEY (@vibiz/app).

#Examples

A Next.js app on another host that only takes payments:

vibiz init shop --resources none
vibiz domains add shop.example.com --elsewhere      # agent key: then its TXT record + verify
vibiz payments products add Pro --amount 900 --interval month --lookup-key pro-monthly
vibiz payments webhook https://shop.example.com/api/vibiz/webhook   # owner key (production); agent keys set development

Once the domain is trusted, the live webhook defaults to https://shop.example.com/api/vibiz/webhook anyway; an agent key can set a live URL on one of the project's domains with PATCH /v1/projects/<id>/payments?env=production.

import { vibiz } from '@vibiz/app';

const { url } = await vibiz.payments.checkout({
  lookup_key: 'pro-monthly',
  user: session.userId,
  success_url: 'https://shop.example.com/thanks',
  cancel_url: 'https://shop.example.com/pricing',
});
// redirect the buyer to url; await vibiz.webhooks.receive(req) in the webhook route (only the app key needed)

A script that sends a daily report by email:

vibiz init reports --resources email
VIBIZ_APP_KEY=vz_app_… node report.mjs

import { vibiz } from '@vibiz/app';
await vibiz.email.send({ to: 'team@example.com', subject: 'Daily report', text: body });

A plain HTML site with analytics: vibiz init mysite --resources analytics, vibiz domains add mysite.com --elsewhere, then paste vibiz analytics snippet before </head> (Analytics).

#Good to know

• The app key is a server secret. @vibiz/app refuses to run in a browser. A plain site or a mobile app calls its own backend (or a small function) that holds the key; only the analytics tag's site key is public.
• Add every domain the app answers on. Sign-in and analytics refuse other origins (www. comes with the domain). An agent may add one; sign-in trusts it once its TXT record proves it (or the owner confirms it).
• Payment webhooks have no default without hosting. On Vibiz hosting events go to https://<slug>.vibiz.app/api/vibiz/webhook by themselves; elsewhere the owner sets the URL, or an agent sets one on a domain the owner already added. Setting it puts VIBIZ_WEBHOOK_SECRET in the env.
• Rotations follow on the next boot. Values loaded with the key are read fresh each start; pasted values don't follow a rotation.
• What needs Vibiz hosting: deploys, previews and rollback; buying a domain (it is served there at once: connect one bought elsewhere with --elsewhere instead); and the code in an export (the database and the env guide export without it).
• Add hosting later with vibiz add hosting: every key is then pushed to the host by itself.