Reepolee System
For application teams
A commercially licensed reference implementation for web applications you can run, understand, and maintain yourself.
Engineering approach · Reference implementation
A practical approach to building software that lasts
Products and services
Choose your starting point
ReeWeb
For static sites
A free, zero-dependency static-site generator. Start static; add Reepolee when you need editing, data, or a backoffice.
Work with Reepolee
For organisations
Architecture review, implementation guidance, or a durable custom backoffice built around your actual operations.
Web engineering has become unsustainably complex
Frameworks accumulate layers upon layers. Dependencies grow until upgrading becomes a project of its own. Tooling that promised simplicity now requires dedicated teams to configure and maintain. The cloud, for all its convenience, introduced operational complexity that most organisations never asked for.
- Framework churn - what you chose last year is already legacy.
- Dependency explosion - hundreds of packages for a single page.
- Tooling overhead - build steps, transpilers, bundlers, linters.
- Cloud lock-in - once you commit, leaving costs more than staying.
- Shortened lifecycles - software rewritten every two years because no one can maintain what exists.
Why Reepolee exists
An 8-minute introduction to the engineering philosophy behind Reepolee - the problem, the insight, the principles, and the implementation.
Some engineering principles survive every technology cycle
The industry's collective memory is surprisingly short. Every few years, the same lessons are learned and forgotten. But certain principles have remained valuable across decades of changing technology, not because they are fashionable, but because they are correct.
- Simplicity - each layer you choose not to add is a layer that cannot fail.
- Explicit architecture - code you can read and understand without debugging a framework.
- Server-side rendering - predictable, resilient, infrastructure-friendly.
- Minimal dependencies - the fewer you import, the fewer you maintain.
- Infrastructure ownership - knowing where your software runs means knowing how it behaves.
What would a modern web application look like if we started from first principles?
Instead of asking which framework or platform to adopt, we asked a more fundamental question. The answer is not a list of technologies. It is a set of engineering convictions that determine which technologies are worth using, and which are not.
We prefer
Instead of
Simplicity
Accidental complexity
Standards
Proprietary abstractions
Explicit architecture
Hidden framework magic
Server-side rendering
Client-heavy rendering
Vanilla JavaScript
Large frontend frameworks
Minimal dependencies
Massive dependency trees
Infrastructure ownership
Vendor lock-in
Long-term maintainability
Constant rewrites
Introducing Reepolee
Reepolee is a practical software engineering approach for building long-lived web applications. It is not a framework. Not a starter template. Not a boilerplate. It is a coherent engineering philosophy - a set of principles, patterns, and practices that have been proven across decades of real-world projects.
The Reepolee System
a production-ready reference implementation
The Reepolee System demonstrates every principle in practice. Server-side rendering, vanilla JavaScript, explicit routing, minimal dependencies, secure tunnels, on-premise deployment - each feature exists because the philosophy demands it, not because it is trendy.
- Server-side rendering for predictable, resilient applications.
- Vanilla JavaScript - no framework abstraction layer.
- Explicit routing and architecture - you see how the application is structured.
- Minimal dependencies - a surface you can understand and control.
- Secure tunnels for development and deployment.
- On-premise capability - deploy where you own the infrastructure.
From Engineering Notes
The reasoning behind the decisions
Short essays on the trade-offs, tools, and operational choices that shape the Reepolee System.
-
Why Scripting?
Why Reepolee builds with plain TypeScript scripts: they let platform quirks be absorbed into readable code you own, in one place, rather than leaking into configuration, plugins, or setup instructions.
Read note -
Boring UI Wins
On why standardized, predictable UI wins over the life of a product - covering component learning curves, layout conventions, browser-native features, accessibility, maintenance debt, and why the best interface is the one nobody notices.
Read note -
The Generator Pattern, Not a Library
Why Reepolee uses a code generator instead of a library, and what that choice means for security, maintainability, and the surface of change in your own project.
Read note
Need help adopting the Reepolee Approach?
Reepolee Labs provides architecture reviews, mentoring, and implementation guidance for teams adopting Reepolee. These services are optional - the approach is designed to be self-adoptable - but direct access to the people who developed it can accelerate your journey.
Engineering decisions
Organisational value
Minimal dependencies
Lower upgrade and security risk
Vanilla JavaScript
Easier onboarding and hiring
Server-side rendering
Simpler infrastructure
Explicit architecture
Lower maintenance costs
On-premise deployment
Infrastructure ownership and compliance
Stable conventions
Longer software lifespan
Explore the ReeWeb alpha
ReeWeb is our free-of-charge proprietary static site generator. It is available now as a public alpha download under its included license; run bun dev for live development or bun ssg for a rendered static site.