At Reinos, we’re always looking for ways to improve the developer experience — especially when it comes to building and testing in local environments. That’s why we’re excited to announce that our modules now support a wider range of domains specifically for local development.
Why this matters
Previously, we only allowed a small selection of development domains, based on a general rule of thumb:
"Always enter either one Live or one Test URL. For a local environment, always use *.dev, *.local, *.test or *.localhost, as these TLDs are free to use."
That worked fine for many, but it didn’t cover modern dev workflows — especially when using tools like Docker, DDEV, Laravel Valet, or PaaS solutions like Heroku and AWS.
What’s new?
We've now aligned our local development policy with ExpressionEngine’s official guidelines, meaning you can freely use our modules in your local environment if you use any of the following approved top-level domains or development platforms.
✅ Approved Top-Level Domains
- .acc
- .acceptance
- .demo
- .example
- .invalid
- .loc
- .local
- .localhost
- .sandbox
- .stage
- .staging
- .test
- .testing
- .vm
✅ Approved PaaS Domains
- amazonaws.com
- elasticbeanstalk.com
- frb.io
- herokuapp.com
- xip.io
- localtest.me
- ddev.site
- lndo.site
What does this mean for you?
If you're running your local site on a domain like myproject.ddev.site or app.localhost, you can now use our modules without any license restrictions in development mode. This makes setup easier and removes friction from the dev-to-deploy pipeline.
Final thoughts
This change is all about flexibility and compatibility. Whether you're running a basic MAMP setup or a full container-based environment, we want our modules to just work. We’ll continue to follow ExpressionEngine’s lead in making local development more accessible and more developer-friendly.
Have questions or need support setting up your local domain? Get in touch, we’re happy to help!
5/8/2025