When we chose the technology for SQRL, we were looking for a foundation that would last years of development, be secure by default and have developers you can hire. Laravel met all three conditions.
A stable foundation, not an experiment
Laravel is the most widely used framework for PHP. It ships regular releases with a clearly defined support window, so we know when and how to update applications.
PHP also runs on almost any hosting or your own server, so running SQRL requires no special infrastructure.
Secure by default
CSRF protection, safe database access through the ORM, password hashing and authorization rules are part of the framework. We don't have to rewrite them or add them with a plugin.
SQRL's access control is built on these foundations: roles, ACLs and granular permissions for every user.
Security isn't a feature we add at the end. It's part of the architecture from the first line.
Queues for long-running operations
Importing thousands of listings, syncing with a CRM or processing images must not slow down your visitors. Laravel has queues in its core, so these jobs run in the background.
Support for long-running operations is one of the differences you'll see in our comparison with WordPress and Strapi.
Ecosystem and developers
Laravel is used by a huge developer community. Its patterns are familiar and its documentation is excellent, so anyone who has worked with the framework gets up to speed quickly.
That's why you're not tied to a single vendor: your own team or any other developer who knows Laravel can continue building on SQRL. The license for your domain is perpetual.
What it means for you
A ready, tested foundation lowers development costs: you only pay for features that are unique to your project. New features are built with templates and plugins, without touching the core.
And if you want to run the application in your own environment, Laravel makes that easy.
We'll show you SQRL using an example close to your project.