Skip to content
Saleor
Esc
↑↓navigate↵open⌘Jpreview
On this page

Engine and Application Hosting

Engine hosts and scales storefronts, apps, integration code, jobs and agents alongside Saleor’s commerce core. It is an open beta available to all Saleor Cloud customers, without an invitation.

What Can Run on Engine?

Host Paper, your own storefront in another stack, or custom code that connects Saleor to your business systems. Use Engine to keep application hosting alongside your Cloud environment, or choose an external host for some or all of your custom code.

Databases, Caches and State

Engine does not provide a database, Redis, Valkey or equivalent data service for your applications. There are two ways to manage state:

  • Use Saleor’s GraphQL API and dynamic modelling for state that fits the commerce model.
  • Connect your application to an external service, such as RDS, Turso or an externally hosted cache.

Choose according to the data model and access patterns. Using an external data service does not require moving the application off Engine.

Usage and Hosting Economics

Engine usage draws down your plan’s API usage entitlement. Engine works for most merchants, but traffic that generates little GMV can consume that entitlement faster than sales replenish it. External hosting may be more economical for those workloads.

High traffic alone is not the deciding factor. Compare expected Engine usage, API calls, purchased GMV and excess-usage charges with the cost of an external host. External storefronts and integrations still consume API allowance when they call Saleor.

See fair API usage for the entitlement model.

Implementation Paths

Last updated on November 16, 2026

Was this page helpful?