> ## Documentation Index
> Fetch the complete documentation index at: https://docs.deep.space/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> What DeepSpace is, who it's for, and why you'd use it.

DeepSpace is an SDK for building real-time collaborative applications on Cloudflare Workers. The frontend is a standard Vite + React project. The backend is a Hono-based Cloudflare Worker. The SDK provides React providers and hooks, Durable Object base classes for sync and presence, a CLI, and a deploy pipeline that takes a project from `npm create` to a live URL.

## What you get out of the box

When you scaffold a new app, you get a working starter with all of this already wired up:

* **Authentication** - Better Auth with GitHub and Google OAuth. JWTs are minted by the DeepSpace platform's auth service; you don't run an auth server.
* **Data sync** - A SQLite-backed Durable Object per app, with WebSocket-based subscriptions, optimistic local mutations, and per-collection role-based access control.
* **Real-time primitives** - Channel messaging, DMs, reactions, presence (live cursors, typing, viewport), Yjs-backed collaborative text and shapes, and a tick-based authoritative game-loop room.
* **File storage** - Per-app scoped R2 uploads.
* **AI** - Streamed Claude, OpenAI, and Cerebras with multi-turn tool use, persistent chat history, and automatic context compaction.
* **Payments** - Stripe subscriptions, one-time products, ad-hoc charges, refunds, and self-service billing portals.
* **Scheduled tasks** - Per-app cron via a built-in Durable Object, with an admin monitor hook.
* **Background jobs** - Durable, observable background work (AI generations, exports, fan-outs) with live progress, cancel, and retry - jobs survive isolate restarts.
* **Third-party integrations** - A proxy that fronts 215+ external API endpoints (OpenAI, Anthropic, Stripe, Gmail, Calendar, LiveKit, finance, search, media, and more), with billing routed to the developer or the end-user.
* **Custom Cloudflare bindings** - Declare Vectorize, KV, D1, Queues, Browser Rendering, Hyperdrive, or your own R2 buckets and the deploy pipeline auto-provisions them.
* **Custom domains (optional)** - Apps ship on `<name>.app.space` by default; bring your own `.com`, `.ai`, `.io`, or other domain via the CLI when you want a branded URL.

## Who it's for

DeepSpace fits applications where state is shared across users or sessions. Common use cases:

* Real-time updates across multiple browsers or devices
* Per-user roles and access control on shared data
* Collaborative editing (text, shapes, canvas)
* Channel-based or DM-style messaging
* A streamed AI chat surface with tool use
* A billing model with subscriptions or one-time purchases
* Cron jobs or background work without standing up new infrastructure

Apps deploy to Cloudflare's global network, so requests terminate close to the user.

## What it isn't

* **Not a no-code platform.** You write TypeScript and React. The CLI scaffolds, runs, and deploys - it doesn't generate features.
* **Not a UI library.** Scaffolds include a shadcn-style primitives kit and 15 theme presets, but you own the design.
* **Not a backend framework.** The worker is a normal Hono app; you can add routes, middleware, and bindings freely.
* **Not a SaaS lock-in.** Apps deploy to Cloudflare Workers - you own the runtime, the data sits in your own Durable Objects, and you can eject at any time.

## Architecture at a glance

A DeepSpace app has two parts. **Your worker** is a Cloudflare Worker that serves the React SPA, exposes API routes, and owns the per-app Durable Objects holding records, Yjs documents, canvases, presence, and scheduled jobs. **The DeepSpace platform** is a set of shared workers - auth, billing, integrations, cross-app data - that your worker calls over service bindings. You deploy your worker; the platform workers are managed by DeepSpace.

See [Architecture](/concepts/architecture) for the full breakdown.

## Next steps

* [Quickstart](/get-started/quickstart) - scaffold and deploy your first app.
* [Installation](/get-started/installation) - prerequisites, account setup, and CLI login.
* [Project structure](/get-started/project-structure) - a tour of the scaffolded files.
* [Architecture](/concepts/architecture) - workers, Durable Objects, and scopes.