FullStacked Cloud Documentation

How code inside a FullStacked Cloud project (index.tsx, index.ts, actions/<name>.ts) runs in the FullStacked Runtime and reaches the platform: the signed-in user, managed data, Edge tunnels, project actions and every public endpoint.

Rules for project code

UI and logic share one runtime context: there is no local backend server (node:http servers and child_process are unavailable). Import your functions and call them.
Call platform services with absolute URLs from process.env (${process.env.AUTH_URL}/api/v1/me) and Authorization: Bearer ${process.env.AUTH_TOKEN}. A relative fetch("/...") reads the project's static files.
Reach managed data and private services through fullstacked/tunnel with the compound token ${process.env.AUTH_TOKEN}:${process.env.<NAME>_TOKEN}.
Start every file that contains JSX, the entrypoint included, with import React from "react";: the entrypoint always compiles JSX to React.createElement.

Topics

Topic	Slug	Machine-readable
FullStacked Runtime	`runtime`	md · json
Current User (/api/v1/me)	`me`	md · json
Injected process.env	`project-runtime`	md · json
Managed Data	`data`	md · json
Edge & LAN Tunnels	`tunnels`	md · json
Project Actions	`actions`	md · json
Runtime Sign-In & BYOA	`auth-byoa`	md · json
Platform API Reference	`api-reference`	md · json

For AI agents and scripts

Everything as Markdown: https://docs.fullstacked.cloud/?format=md (one topic: https://docs.fullstacked.cloud/<slug>?format=md).
JSON catalog (topics, endpoints, data limits): https://docs.fullstacked.cloud/?format=json; endpoints only: https://docs.fullstacked.cloud/api/v1/endpoints.
Search: https://docs.fullstacked.cloud/?q=<text>&format=md; filter endpoints by service: ?service=auth|git|tunnels|data|mcp|install|docs.
MCP (https://mcp.fullstacked.cloud/mcp): docs_list, docs_get({ topic }) and the resources fullstacked://docs / fullstacked://docs/{topic}.