Hosting Statamic on Cloudflare Pages
In this article we explore how we moved Swiftmade.co, our Statamic powered website to Cloudflare Pages
Swiftmade helps startups and scale-ups in Europe and the UK
to launch and grow online products.
Need something built from scratch?
We take your idea and turn it into a fully-functional product. Weekly demos. Clean code. No surprises!
Perfect for
Need to boost your existing team?
Our devs show up. They think with you. They deliver. They're surprisingly pleasant to work with.
Perfect for
Swiftmade not only improved our existing software, but during the process they also saved us months worth of work by moving our calculations from Excel to easy to understand web interfaces.
Chair of METU Petroleum Research Center
Swiftmade greatly accelerated the development of our realtime fleet management software which configures, monitors and supervises our robots. They quickly understood our needs and executed our ideas in record time.
Co-founder & CIO of Milvus Robotics
After analyzing our Comprehensive School Safety Risk, Damage and Needs Assessment assistance program, Swiftmade architected a highly customizable Cloud-based survey solution for us. This design now lets us introduce our program in new territories with speed and reliability.
President of IMAGINS
We use battle-tested technologies to build reliable, scalable, and maintainable applications.
Our go-to framework for reliable, modern web apps.
Progressive framework for modern web apps.
Powerful admin panels, minus the grunt work.
Finally, a CMS your team won't hate using.
Scalable backend solutions with TypeScript.
Building rich user interfaces with React ecosystem.
Cloud infrastructure that scales with your needs.
Seamless payment solutions for modern businesses.
In this article we explore how we moved Swiftmade.co, our Statamic powered website to Cloudflare Pages
Using Plausible in your Laravel site and want Plausible to ignore your visits? We got a package for you!
We were getting ~100 spam requests per second, which filled up our access.log file. Here's how we fixed that.