Skip to main content

Can I Use FlyingPress on a Staging or Local Development Site?

Updated this week

Yes, FlyingPress supports staging and development environments, and they do not count against your license limit.

Allowed domains (not counted in license usage):

Development & local domains:

  • localhost

  • Domains ending in .dev, .local, .test

  • Domains starting with dev., staging., staging[0-9], stage., test., testing.

Popular staging platforms:

  • .bigscoots-staging.com

  • .cloudwaysapp.com

  • .closte.com

  • .e.wpstage.net

  • .flywheelstaging.com

  • .instawp.xyz

  • .kinsta.cloud

  • .onrocket.site

  • .pantheonsite.io

  • .pressdns.com

  • .runcloud.link

  • .servebolt.com

  • .sg-host.com

  • .stacks.run

  • .tastewp.com

  • .updraftclone.com

  • .wpdns.site

  • .wpengine.com

  • .zipwp.link

Note on local environments

FlyingPress won’t work properly on local machines (like localhost) because our cloud servers are unable to access your site to fetch pages and generate optimizations such as critical CSS, unused CSS removal, and image processing.

Example

If you have a single site license, you can activate FlyingPress on both example.com and staging.example.com without using up an extra license slot.

This allows safe testing and optimization before pushing changes live.

Did this answer your question?