Quickstart

Result Backend is your app’s hosted backend: Postgres, user auth, file storage, serverless functions, realtime channels, AI models, transactional email, and Stripe/Razorpay payments. It is already provisioned — nothing to install or host. Your app’s page in the Result dashboard has three credentials. Put them in .env.local:

NEXT_PUBLIC_BACKEND_URL=...        # the backend's base URL
NEXT_PUBLIC_BACKEND_ANON_KEY=...   # publishable client key (safe in browsers)
BACKEND_ADMIN_KEY=...              # admin key — server/terminal ONLY

Four steps

Persist the backend rules into your repo (writes AGENTS.md/CLAUDE.md so every future AI coding session knows how this backend works):
npx @resultdev/cli init
Install the SDK:
npm install @resultdev/sdk

Create the client:

// lib/backend.ts
import { createClient } from "@resultdev/sdk";

export const backend = createClient({
  baseUrl: process.env.NEXT_PUBLIC_BACKEND_URL!,
  anonKey: process.env.NEXT_PUBLIC_BACKEND_ANON_KEY!,
});

Make a call:

const { data, error } = await backend.database.from("todos").select();

The one rule

App code → SDK with the publishable key. Covered in the SDK section.
One-time setup (tables, migrations, buckets, channels, functions, secrets, payment keys) → CLI with the admin key, from the terminal. Covered in the CLI section.

Never hand-roll HTTP against the backend, and never let BACKEND_ADMIN_KEY reach the browser. Next: create your first table, then read Database.

Getting started

SDK

CLI

Guides

Four steps

The one rule

​Four steps

​The one rule

Four steps

The one rule