docs: Add Flash documentation

.cursor/rules/rp-styleguide.mdc

@@ -5,7 +5,7 @@ alwaysApply: true
 ---
 
 Always use sentence case for headings and titles.
-These are proper nouns: Runpod, Pods, Serverless, Hub, Instant Clusters, Secure Cloud, Community Cloud, Tetra.
+These are proper nouns: Runpod, Pods, Serverless, Hub, Instant Clusters, Secure Cloud, Community Cloud, Flash.
 These are generic terms: endpoint, worker, cluster, template, handler, fine-tune, network volume.
 
 Prefer using paragraphs to bullet points unless directly asked.

CLAUDE.md

@@ -98,7 +98,7 @@ Follow the Runpod style guide (`.cursor/rules/rp-styleguide.mdc`) and Google Dev
 ### Capitalization and Terminology
 
 - **Always use sentence case** for headings and titles
-- **Proper nouns**: Runpod, Pods, Serverless, Hub, Instant Clusters, Secure Cloud, Community Cloud, Tetra
+- **Proper nouns**: Runpod, Pods, Serverless, Hub, Instant Clusters, Secure Cloud, Community Cloud, Flash
 - **Generic terms** (lowercase): endpoint, worker, cluster, template, handler, fine-tune, network volume
 
 ### Writing Style

community-solutions/ohmyrunpod/overview.mdx

@@ -17,10 +17,10 @@ Check the repository for additional features, updates, and documentation: [githu
 ## Key features
 
 <CardGroup cols={2}>
-  <Card title="Easy File Transfer" icon="arrow-right-arrow-left">
+  <Card title="Easy File Transfer" icon="arrow-right-arrow-left" horizontal>
     Simplified file transfer between your local machine and Runpod instances using SFTP or Croc
   </Card>
-  <Card title="Automatic SSH Setup" icon="key">
+  <Card title="Automatic SSH Setup" icon="key" horizontal>
     Automatically configures SSH access with secure key generation and password management
   </Card>
 </CardGroup>

community-solutions/overview.mdx

@@ -17,31 +17,31 @@ Community tools and solutions are provided as-is and maintained by their creator
 Explore these community-created tools that can enhance your Runpod workflow:
 
 <CardGroup cols={1}>
-  <Card 
+  <Card horizontal
     title="ComfyUI to API" 
     icon="wand-magic-sparkles"
     href="/community-solutions/comfyui-to-api/overview"
   >
     Web-based tool that analyzes ComfyUI workflows and automatically generates Dockerfiles and GitHub repositories for deployment on Runpod Serverless.
   </Card>
 
-  <Card 
+  <Card horizontal
     title="OhMyRunPod" 
     icon="rocket"
     href="/community-solutions/ohmyrunpod/overview"
   >
     Python package for easy SFTP setup and file transfers. Simplifies connecting to your Pods with file transfer software like FileZilla.
   </Card>
 
-  <Card 
+  <Card horizontal
     title="SSH password setup & migration tools" 
     icon="arrows-rotate"
     href="/community-solutions/ssh-password-migration/overview"
   >
     Bash and Python scripts for migrating data between Runpod instances when you need to move Pods or backup data.
   </Card>
 
-  <Card 
+  <Card horizontal
     title="CopyParty file manager" 
     icon="folder-open"
     href="/community-solutions/copyparty-file-manager/overview"

containers.mdx

@@ -2,35 +2,35 @@
 title: "Containers"
 ---
 
-<Card href="/tutorials/introduction/containers">
+<Card href="/tutorials/introduction/containers" horizontal>
 ## 📄️ Overview
 
 Learn how to build and deploy applications on the Runpod platform with this set of tutorials, covering tools, technologies, and deployment methods, including Containers, Docker, and Serverless implementation.
 
 </Card>
 
-<Card href="/tutorials/introduction/containers/">
+<Card href="/tutorials/introduction/containers/" horizontal>
 ## 📄️ Intro to containers
 
 Discover the world of containerization with Docker, a platform for isolated environments that package applications, frameworks, and libraries into self-contained containers for consistent and reliable deployment across diverse computing environments.
 
 </Card>
 
-<Card href="/tutorials/introduction/containers/create-dockerfiles">
+<Card href="/tutorials/introduction/containers/create-dockerfiles" horizontal>
 ## 📄️ Dockerfile
 
 Learn how to create a Dockerfile to customize a Docker image and use an entrypoint script to run a command when the container starts, making it a reusable and executable unit for deploying and sharing applications.
 
 </Card>
 
-<Card href="/tutorials/introduction/containers/persist-data">
+<Card href="/tutorials/introduction/containers/persist-data" horizontal>
 ## 📄️ Persist data outside of containers
 
 Learn how to persist data outside of containers by creating named volumes, mounting volumes to data directories, and accessing persisted data from multiple container runs and removals in Docker.
 
 </Card>
 
-<Card href="/tutorials/introduction/containers/docker-commands">
+<Card href="/tutorials/introduction/containers/docker-commands" horizontal>
 ## 📄️ Docker commands
 
 Runpod enables BYOC development with Docker, providing a reference sheet for commonly used Docker commands, including login, images, containers, Dockerfile, volumes, network, and execute.

docs.json

@@ -9,6 +9,7 @@
   },
   "background": {},
   "styling": {
+    "css": "/style.css",
     "codeblocks": {
       "theme": {
         "dark": "github-dark",
@@ -44,6 +45,55 @@
               "get-started/mcp-servers"
             ]
           },
+          {
+            "group": "Flash",
+            "pages": [
+              "flash/overview",
+              "flash/quickstart",
+              "flash/pricing",
+              "flash/create-endpoints",
+              "flash/custom-docker-images",
+              {
+                "group": "Configure resources",
+                "pages": [
+                  "flash/configuration/storage",
+                  "flash/configuration/gpu-types",
+                  "flash/configuration/cpu-types",
+                  "flash/configuration/parameters",
+                  "flash/configuration/best-practices"
+                ]
+              },
+              "flash/execution-model",
+              "flash/troubleshooting",
+              {
+                "group": "Build apps",
+                "pages": [
+                  "flash/apps/overview",
+                  "flash/apps/build-app",
+                  "flash/apps/initialize-project",
+                  "flash/apps/customize-app",
+                  "flash/apps/local-testing",
+                  "flash/apps/apps-and-environments",
+                  "flash/apps/deploy-apps",
+                  "flash/apps/requests"
+                ]
+              },
+              {
+                "group": "CLI reference",
+                "pages": [
+                  "flash/cli/overview",
+                  "flash/cli/init",
+                  "flash/cli/login",
+                  "flash/cli/run",
+                  "flash/cli/build",
+                  "flash/cli/deploy",
+                  "flash/cli/env",
+                  "flash/cli/app",
+                  "flash/cli/undeploy"
+                ]
+              }
+            ]
+          },
           {
             "group": "Serverless",
             "pages": [
@@ -168,13 +218,13 @@
             "pages": [
               "public-endpoints/overview",
               "public-endpoints/quickstart",
+              "public-endpoints/reference",
               "public-endpoints/requests",
               "public-endpoints/ai-sdk",
               "public-endpoints/ai-coding-tools",
               {
                 "group": "Models",
                 "pages": [
-                  "public-endpoints/reference",
                   {
                     "group": "Image models",
                     "pages": [
@@ -358,6 +408,14 @@
               "tutorials/serverless/run-gemma-7b"
             ]
           },
+          {
+            "group": "Flash",
+            "pages": [
+              "tutorials/flash/text-generation-with-transformers",
+              "tutorials/flash/image-generation-with-sdxl",
+              "tutorials/flash/build-rest-api-with-load-balancer"
+            ]
+          },
           {
             "group": "Pods",
             "pages": [
@@ -823,6 +881,10 @@
     {
       "source": "/hub/public-endpoint-reference",
       "destination": "/public-endpoints/reference"
+    },
+    {
+      "source": "/flash/endpoint-functions",
+      "destination": "/flash/create-endpoints"
     }
   ]
 }

flash/apps/apps-and-environments.mdx

@@ -0,0 +1,158 @@
+---
+title: "Apps and environments"
+sidebarTitle: "Apps and environments"
+description: "Understanding Flash's two-level deployment structure for organizing projects and managing deployments."
+---
+
+Flash uses a two-level organizational structure for deployments: **apps** and **environments**. Understanding this structure helps you organize projects, manage multiple deployment stages, and isolate resources effectively.
+
+## Flash apps
+
+A **Flash app** is a namespace on Runpod's backend that groups all resources for a single project. The app itself is just metadata—actual cloud resources (endpoints, volumes) are created when you deploy to an environment.
+
+An app consists of:
+
+- **App registry entry**: Metadata in Runpod's system (namespace, project identifier).
+- **Environments**: Different deployment stages (dev, staging, production).
+- **Builds**: Versioned tarball artifacts containing your code and dependencies.
+- **Serverless endpoints**: Running infrastructure created per environment.
+
+Apps are created automatically when you first run `flash deploy`, or explicitly with `flash app create <name>`.
+
+### App hierarchy
+
+<Tree>
+  <Tree.Folder name="Flash App (my-project)" defaultOpen>
+    <Tree.Folder name="Environments" defaultOpen>
+      <Tree.Folder name="dev" defaultOpen>
+        <Tree.Folder name="Endpoints" defaultClosed>
+          <Tree.File name="lb_worker" />
+          <Tree.File name="gpu_worker" />
+          <Tree.File name="cpu_worker" />
+        </Tree.Folder>
+        <Tree.Folder name="Volumes" defaultClosed>
+          <Tree.File name="model-cache" />
+        </Tree.Folder>
+      </Tree.Folder>
+      <Tree.Folder name="staging" defaultOpen>
+        <Tree.Folder name="Endpoints" defaultClosed>
+          <Tree.File name="lb_worker" />
+          <Tree.File name="gpu_worker" />
+          <Tree.File name="cpu_worker" />
+        </Tree.Folder>
+        <Tree.Folder name="Volumes" defaultClosed>
+          <Tree.File name="model-cache" />
+        </Tree.Folder>
+      </Tree.Folder>
+      <Tree.Folder name="production" defaultOpen>
+        <Tree.Folder name="Endpoints" defaultClosed>
+          <Tree.File name="lb_worker" />
+          <Tree.File name="gpu_worker" />
+          <Tree.File name="cpu_worker" />
+        </Tree.Folder>
+        <Tree.Folder name="Volumes" defaultClosed>
+          <Tree.File name="model-cache" />
+        </Tree.Folder>
+      </Tree.Folder>
+    </Tree.Folder>
+    <Tree.Folder name="Builds" defaultOpen>
+      <Tree.File name="build_v1" />
+      <Tree.File name="build_v2" />
+      <Tree.File name="build_v3" />
+    </Tree.Folder>
+  </Tree.Folder>
+</Tree>
+
+
+## Environments
+
+An **environment** is an isolated deployment stage within a Flash app (e.g., `dev`, `staging`, `production`). Each environment has its own endpoints, build version, volumes, and deployment state. Environments are completely independent—deploying to `dev` has no effect on `production`.
+
+An environment contains:
+
+- **Deployed endpoints**: Serverless workers for your `@Endpoint` functions.
+- **Build version**: The specific code version running in this environment.
+- **Volumes**: Persistent storage attached to workers.
+- **State**: Current deployment status (deploying, deployed, failed).
+
+Environments are created automatically when you deploy with `--env <name>` or explicitly with `flash env create <name>`.
+
+### Environment states
+
+Environments can be in several states:
+
+| State | Description |
+|-------|-------------|
+| `deploying` | Deployment in progress (building artifacts, provisioning endpoints) |
+| `deployed` | Successfully deployed and running |
+| `failed` | Deployment failed (check logs in the [Runpod console](https://www.runpod.io/console/serverless)) |
+| `updating` | Configuration update in progress |
+
+## Builds and deployments
+
+When you run `flash deploy`, Flash creates and uploads a build artifact, then provisions endpoints:
+
+### Build process
+
+1. **Create tarball**: Flash packages your code into `.flash/artifact.tar.gz` containing:
+   - Worker Python files (`lb_worker.py`, `gpu_worker.py`, `cpu_worker.py`).
+   - Pre-installed dependencies (bundled during build).
+   - Deployment manifest (`flash_manifest.json`).
+   - Auto-generated handler code.
+
+2. **Upload artifact**: The tarball is uploaded to Runpod's storage and associated with your app as a versioned "build".
+
+3. **Provision endpoints**: For each resource configuration, Flash creates a Serverless endpoint that:
+   - Runs on pre-built Flash Docker images (`runpod/flash:latest` or `runpod/flash-cpu:latest`).
+   - Extracts your tarball and executes your code.
+   - Scales automatically based on load.
+
+4. **Activate environment**: The environment is linked to the build and endpoints.
+
+<Tip>
+You're **not** building custom Docker images. Flash uses pre-built images that extract your tarball and run your code. This is why deployments are fast (no image build step) and limited to 500 MB (code and dependencies only).
+</Tip>
+
+## Common environment patterns
+
+### Single environment (simple projects)
+
+For small projects or solo development, use a single environment:
+
+```bash
+flash deploy --env production
+```
+
+All deployments go to `production`. Simple, but no testing isolation.
+
+### Multiple environments (team projects)
+
+For team projects, use separate environments for development, testing, and production:
+
+```bash
+flash deploy --env dev        # Development and testing
+flash deploy --env staging    # QA and pre-production validation
+flash deploy --env production # Live user-facing deployment
+```
+
+Each environment is completely isolated. Deploy to `dev` for testing, `staging` for QA approval, then `production` for users.
+
+## Managing apps and environments
+
+Use the CLI to manage your apps and environments:
+
+```bash
+# Apps
+flash app list              # List all apps
+flash app get <name>        # View app details
+flash app delete <name>     # Delete app and all environments
+
+# Environments
+flash env list              # List environments in current app
+flash env get <name>        # View environment details
+flash env delete <name>     # Delete specific environment
+```
+
+<Warning>
+Deleting an app or environment is irreversible. All endpoints and configuration are permanently removed.
+</Warning>