We build software that makes your website build better.
Web.Mobile.Edge.
Custom websites, apps and software with clean code and simple architecture. M4RF’s development work, documented in plain words.
Tell us about your projectStackThe technologies we choose by default
Few technologies, well chosen.
A small set of tools we know inside out. When a project calls for something else we say so, and explain why.
Frontend.
- ReactModern interfaces from reusable components, for dynamic web applications.
- AstroFast, content-rich websites, with JavaScript only where it’s needed.
- LitStandard Web Components, reusable across any stack.
- TailwindUtility-first CSS for consistent interfaces that are easy to maintain.
Backend.
- NestJSStructured, scalable and type-safe Node.js APIs and backends.
- HonoAn ultra-light framework for APIs on the edge and serverless.
Mobile.
- React NativeNative iOS and Android apps from a single codebase.
Edge and data.
- Cloudflare WorkersCode that runs close to users, with minimal latency and global scale.
- PostgreSQLA solid relational database for complex data and transactions.
- RedisIn-memory data for caching, sessions and message queues.
WikiMethod, technology, guarantees
How we work, documented.
- 01IntroductionModern Development GuideWhat makes a web or mobile project successful in 2025: the m4rf.dev vision.
- 02ProcessOur MethodologyAgile approach and project management
- 03TechnicalTechnology StackThe technological stack we use for our projects
- 04PolicyGuarantees & OwnershipQuality standards and code rights
NotesThe technical articles, on m4rf.it
What we learn building, in writing.
- WebsitesAstro and content architecture
- AppsReact Native for business apps
- EdgeEdge-first applications
- MethodAI in the development workflow, with discipline
- WebsitesAstro 6: server islands and responsive images
- DataDirectus and the headless CMS
- WebsitesHeadless architecture
Do you have a website, an app or software to build?
Tell us about the project and where you’re starting from. We’ll reply with how we’d set it up and what we’d do first.