E-commerce solution
Run Medusa Locally with FlyEnv
Medusa projects use Node.js, PostgreSQL, Redis, and often a local proxy. FlyEnv keeps this TypeScript commerce stack organized for local development.
Local project stack
Services FlyEnv can manage around Medusa
About Medusa
Medusa is a composable commerce platform for building custom stores and commerce services with Node.js and TypeScript. Its modules and workflows model products, carts, orders, promotions, payments, fulfillment, and custom business processes without dictating a storefront.
A Medusa backend commonly uses Node.js and PostgreSQL, and includes its Admin at `/app` on the backend origin. Redis is relevant when the backend configures Redis-backed infrastructure; simple v2 development can use local providers. A custom storefront is a separate application when the project has one, while payment, fulfillment, search, and file providers should be run or mocked according to the integrations under development.
Core capabilities
- Commerce Modules
- Workflows
- Store APIs
- Admin APIs
- Promotion Engine
- Provider Interfaces
Common use cases
- Custom commerce backends
- Headless store frontends
- Marketplace and multi-vendor extensions
- Subscription or B2B commerce
- Fulfillment and payment integrations
Medusa local development coordinates a commerce service and providers
Product flows are only credible locally when the selected data, cache, and provider boundaries are represented.
- Node.js Medusa backend
- Runs Medusa CLI commands, the commerce API, and project-specific workflows.
- PostgreSQL
- Stores commerce entities and is a standard Medusa backend dependency.
- Redis
- Run it only when the backend configures Redis-backed infrastructure; simple v2 development can use local providers.
- Bundled Admin and custom storefront
- Use the backend Admin at `/app` (for example, `localhost:9000/app`); run a separate Node.js server only for a custom storefront.
- Commerce providers
- Use sandbox or local substitutes for configured payment, fulfillment, search, and file providers.
Project resources
For installation commands, supported versions, and project-specific configuration, refer to the official Medusa documentation.
Typical local stack
The exact services depend on the project, its release, and its local configuration. This is a common local setup, not a fixed requirement.
| Component | Typical role |
|---|---|
| Node.js | Runs Medusa services and tooling. |
| PostgreSQL | Stores commerce data. |
| Redis | Supports events, cache, or workflow services. |
| NginxCaddy | May proxy local storefront and API domains. |
How FlyEnv helps
Match Node.js versions
Keep the runtime compatible with Medusa.
Start commerce dependencies together
Run PostgreSQL and Redis with the API.
Use local HTTPS
Test storefront and payment integrations securely.
Set up the local environment
Project installation stays with the upstream documentation. FlyEnv manages the runtimes, databases, web servers, and supporting services around it.
- 1Follow Medusa documentation for project setup.
- 2Select the required Node.js runtime.
- 3Start PostgreSQL and Redis.
- 4Configure local API and storefront domains when needed.
Related solutions
Ready to run Medusa locally?
Use FlyEnv to manage the runtimes, databases, web servers, and services around your local Medusa environment.