Welcome to the CranL Engineering Blog
Every team building software has opinions, discoveries, and hard-won lessons that never make it out of Slack threads or internal docs. We decided to change that.
This blog is where the CranL team writes publicly about what we’re building, how we’re building it, and what we’ve learned along the way. No polished marketing. Just real engineering.
what cranl is
CranL is a PaaS that makes deployment easy and cost-effective. Deploy applications, databases, and templates in seconds — with global infrastructure, GitHub integration, free CDN, SSL, and DDoS protection included. We’re building what we wished existed when we were deploying our own projects.
why we’re writing
Three reasons.
Writing forces clarity. The act of writing a blog post about a technical decision is the best way we know to stress-test that decision. You can’t hide behind “it’s complicated” when you’re explaining it to someone without your context.
It compounds. A detailed post about a problem we solved saves future teammates hours of archaeology through commit history. It may also save you the same hours if you hit the same problem.
Good engineers find good writing. The people we most want to work with tend to produce or consume substantive technical content. This blog is partly a signal.
what you’ll find here
- Engineering — architecture decisions, performance investigations, real benchmarks
- Infrastructure — how we run our global PaaS: deployments, databases, CDN, reliability
- Product — how we translate user feedback into technical requirements and ship without chaos
- Postmortems — when things go wrong (they do), we write up what happened and what changed
how this blog is built
The blog lives at blog.cranl.com and is fully static — generated with Quarto and deployed via CranL itself. No backend, no database, no auth wall. The CSS design tokens are shared with the main site so the two feel like one product.
Techinal Writer and Data Scientist 0xSaad