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

# Welcome to SandyWP

> Create disposable WordPress sandboxes for plugin testing, debugging, demos, and experiments.

SandyWP creates real, isolated WordPress sandboxes that are ready for work and safe to throw away. Use one to test a plugin, reproduce a bug, try a theme, or share a temporary demo.

<img src="https://mintcdn.com/sandy-wp/QrIaogrIPttSMHEN/images/docs/dashboard-sandboxes.png?fit=max&auto=format&n=QrIaogrIPttSMHEN&q=85&s=dba2da3463c52b8ee0b3256e13fecddb" alt="The SandyWP dashboard showing active sandboxes" width="1548" height="500" data-path="images/docs/dashboard-sandboxes.png" />

## Create your first sandbox

You can create a free sandbox from the SandyWP homepage without an account. An account unlocks the dashboard, multiple sandboxes, templates, Git deployment, cloning, and more.

<Steps>
  <Step title="Open the create form">
    From the [SandyWP dashboard](https://app.sandywp.com/app), select **New sandbox**. Or choose **Create a free sandbox** on the [SandyWP homepage](https://sandywp.com).
  </Step>

  <Step title="Choose a name and stack">
    A name is optional. You can also choose a WordPress version, PHP version, region, lifespan, and a saved template.
  </Step>

  <Step title="Wait for the sandbox to be ready">
    SandyWP shows provisioning progress. When the status becomes `ready`, open the public site or select **Auto Login** to enter `wp-admin`.
  </Step>
</Steps>

<Note>
  Guest sandboxes have a fixed seven-hour lifetime. Free accounts can run two active sandboxes and choose a lifespan of up to one week.
</Note>

## Choose a workflow

<CardGroup>
  <Card title="Create a sandbox" href="/guides/create-a-sandbox">
    Configure a fresh WordPress site, a saved template, or a debugging setup.
  </Card>

  <Card title="Open wp-admin" href="/guides/open-wp-admin">
    Sign in with a one-click link or copy the site credentials.
  </Card>

  <Card title="Use the CLI" href="/cli">
    Create, deploy, push, mount, and manage sandboxes from a terminal.
  </Card>

  <Card title="Automate with the API" href="/api-reference">
    Use a personal API key and the generated endpoint reference for supported resources.
  </Card>
</CardGroup>

## What you can do

| Need                              | Start here                                                     |
| --------------------------------- | -------------------------------------------------------------- |
| Edit files in the browser         | [File Manager](/guides/file-manager)                           |
| Change PHP or inspect a database  | [PHP settings](/guides/php) or [Database](/guides/database)    |
| Deploy a plugin or theme from Git | [Git deployment](/guides/git-deployment)                       |
| Start from a reusable snapshot    | [Templates](/guides/templates)                                 |
| Reproduce a setup as JSON         | [Blueprints](/guides/blueprints)                               |
| Put a local site online           | [Push a local site](/guides/push-local-site)                   |
| Work from Slack or GitHub         | [Slack](/guides/slack) or [GitHub PR previews](/guides/github) |

## Next steps

* Read [Core concepts](/concepts) to understand sandboxes, slugs, lifecycle, plans, and regions.
* Read [Plans and limits](/guides/plans) before relying on a sandbox for longer work.
* Create a personal API key only when you need automation; it has full account access.