License
Flick Pro License Agreement, version 1.0 · Last updated August 24, 2026
Flick itself is free. The core library, the Laravel package and the Formr migration tool are MIT licensed, and nothing on this page applies to them. This is about Flick Pro, which is paid.
What follows is the plain-English version. The full agreement ships as the
LICENSE file in the package, and it is the one that governs. If
you want to read it in full before buying, email
support@flickphp.com and we'll send
it over.
What you're buying
Two things, and they end at different times.
A license that doesn't expire. Every version we release while your subscription is active is yours to keep. You can run it in production, on as many projects as you like, for as long as you like. That doesn't stop when your subscription does.
A yearly subscription. While it's active you get new versions, new services, updates for new PHP releases, and access to the private repository. When it ends you stop receiving new versions. You don't stop using the ones you already have, and nothing you've shipped needs touching.
Client work
Build as many client projects as you want. The license stays with you, not with the project. If a client wants to keep getting new versions after you stop working together, or wants to use Pro on work you didn't build for them, they buy their own.
What you can't do
The short version is: don't pass the Software itself along. No redistributing, reselling or sublicensing it, no publishing the source, no sharing your repository access, and don't use it to build a competing form library.
The most common accident is committing a vendor directory containing Flick Pro to a public repository. A private one is fine, and encouraged — see below.
Keep your own copy
Access to the private repository runs with your subscription, and that's where composer installs from. If the subscription lapses, a later deploy can't fetch the package — even though you're still licensed to run it.
So keep a copy of what you're entitled to somewhere you control: commit your vendor directory to your own private repository, or archive the release. The license explicitly allows both, and this is worth doing before you need it.
Refunds
30 days, no questions asked. Email support@flickphp.com and we'll process it — you don't have to explain why.
A refund is different from cancelling. Cancelling ends the subscription and leaves everything you've already paid for running. A refund unwinds the purchase, so the license ends with it and you'd need to take Flick Pro out of any sites using it.
The refund policy has the detail, including how long the money takes to come back and what happens with chargebacks.
License checks
There are none. Flick Pro doesn't phone home, doesn't need a license key, and makes no call to us or to Polar from your server. Access is handled once, at purchase, by adding your GitHub account to the private repository. The privacy policy covers this in full.
Support and warranty
Support is best-effort, by email, at support@flickphp.com. Flick Pro is maintained by one person, so it's honest rather than instant. There's no guaranteed response time.
The Software is provided as is, without warranty. You're responsible for testing it and for the correctness of your own application. Our liability is capped at what you paid in the twelve months before a claim.
Who you're buying from
Flick Pro is sold through Polar, which acts as merchant of record and handles payment, invoicing and sales tax. Your purchase transaction is governed by Polar's terms. Your use of the Software is governed by the Flick Pro License Agreement.
Zer05 Media LLC
support@flickphp.com