# Local development (/docs/local-development)

> For the complete Prisma documentation index, see [llms.txt](https://www.prisma.io/docs/llms.txt). A markdown version of any docs page is available by appending `.md` to its URL.

Run the whole Prisma stack on your machine, with your app on Bun, a local Prisma Postgres database, and local object storage.

Location: Local development

Local development with Prisma means running the stack you deploy, on your machine. You build and test against local pieces, then ship the same code to [Prisma Compute](https://www.prisma.io/docs/compute) and [Prisma Postgres](https://www.prisma.io/docs/postgres) without changing application logic.

Each piece of the platform has a local counterpart:

* **Your app** runs with your framework's dev server or with Bun directly. Prisma Compute runs deployed apps on Bun, so there is no platform emulator to install: the runtime you develop against is the runtime you ship. See [Local app](https://www.prisma.io/docs/local-development/app-development).
* **Your storage** is S3-compatible, so the same client code works against a hosted bucket and a local stand-in. See [Local storage](https://www.prisma.io/docs/local-development/storage).
* **Your database** runs as a local Prisma Postgres instance, started with one command and no Postgres install. See [Local Postgres](https://www.prisma.io/docs/local-development/postgres).

Apps deploy to Compute as [Prisma Composer](https://www.prisma.io/docs/composer) apps, and the pipeline a deploy runs is the same one you run locally: `dev` brings your app up, whether it is one service or several, against local stand-ins for Compute and Prisma Postgres, with no cloud credentials. See [Local development in Composer](https://www.prisma.io/docs/composer/local-development).

- [Local app](https://www.prisma.io/docs/local-development/app-development): Iterate with your framework's dev loop and run the whole app with `dev`.

- [Local storage](https://www.prisma.io/docs/local-development/storage): Use S3-compatible clients against local stand-in buckets and hosted buckets alike.

- [Local Postgres](https://www.prisma.io/docs/local-development/postgres): Start a local Prisma Postgres database with `prisma dev` and manage named instances.

## From local to deployed [#from-local-to-deployed]

The local stack is designed so that switching to the hosted platform is a configuration change, not a code change:

1. [Deploy your app](https://www.prisma.io/docs/prisma-compute/deploy) with `deploy`: the same declarations that ran against local stand-ins provision hosted services, [Prisma Postgres](https://www.prisma.io/docs/postgres) databases, and buckets on the platform.
2. For connections you wired by hand, point `DATABASE_URL` at a hosted Prisma Postgres database and swap local bucket credentials for a minted [access key](https://www.prisma.io/docs/storage).

## Related pages

- [`Choose a Prisma ORM setup path`](https://www.prisma.io/docs/getting-started): Choose the fastest path to try Prisma ORM in a new or existing project.
- [`Console`](https://www.prisma.io/docs/console): Learn how to use the Console to manage and integrate Prisma products into your application.
- [`Introduction to Prisma ORM`](https://www.prisma.io/docs/prisma-orm): Prisma ORM 8 is the current release.
- [`Overview`](https://www.prisma.io/docs/cli): Prisma CLI reference
- [`Overview`](https://www.prisma.io/docs/guides): Practical, step-by-step guides for building with Prisma ORM, each one run end to end before it ships.