Technology
Modern stacks, fast global delivery
Web & SaaS
- Next.js / React
- TypeScript
- API-first backends
- Multi-tenant patterns
Delivery & performance
- Cloudflare CDN
- Global performance
- Observability
- Secure HTTPS delivery
Mobile
- Android / Play Console
- PWAs
- Push notifications
- Store release ops
- Domain mailboxes
- SPF/DKIM/DMARC
- Transactional + campaigns
- Admin consoles
Why this mix
Production habits over fashion
Softlinks bias toward TypeScript, API-first products, Android/Play where mobile matters, and Cloudflare CDN for global speed — so launches stay boring.
CDN
global speed
API
first backends
Play
store muscle
Choices with consequences
Why this stack, and what it costs us
TypeScript end to end means the same people can move between a web app, an API, and a build script without re-learning a toolchain, and it means a rename in a data model surfaces as a compile error rather than a support ticket. The cost is that we are not the fastest team to hand a Python or PHP codebase to.
API-first backends exist because every product we ship eventually grows a second client — a mobile app, a partner integration, an internal report. Building the contract first is cheaper than retrofitting one around an interface that assumed a browser. It does mean more work before the first screen appears.
Cloudflare at the edge gives a school in one country and an agency in another the same first paint, without us running origin servers per region. The trade is that some conveniences of a traditional server are unavailable, which is why image variants on this site are generated at build time rather than resized on request.
Android and Google Play is where our mobile muscle is, because that is where the users of our school and field apps are. iOS-ready workflows are available when a brief requires them, and we say so rather than implying parity we do not practise daily.
Want the same stack for your product?
Share a brief and we will recommend a product, a custom build, or both.