-
-
LeveBase icon
About the Project
LeveBase was inspired by a simple problem: everyday life is managed across too many disconnected tools. Tasks live in one app, notes in another, appointments in a calendar, shopping lists somewhere else, and finances or personal records in yet another system. The result is not a lack of information, but a lack of continuity.
I wanted to build a personal operating system that brings these parts of life together without trying to replace every specialized tool. LeveBase is designed around the idea that your personal information should be connected, portable, and useful in context.
The project combines tasks, notes, events and appointments, goals, shopping lists, personal finance tracking, and personal journals in one workspace. It is designed as a PWA so it can work across desktop and mobile devices, including situations where connectivity is limited.
What I learned
Building LeveBase taught me that a product like this is primarily a systems-design problem, rather than a collection of individual features. The difficult questions are often about relationships between data: how a task relates to a goal, how an event interacts with a task, how shared information should behave, and how users can move their data between systems.
I also learned that privacy and data ownership have to be architectural concerns from the beginning. Personal organization can contain highly sensitive information, so features such as sharing, permissions, encryption, synchronization, and export cannot simply be added at the end.
Another important lesson was resisting unnecessary complexity. Instead of putting AI everywhere, LeveBase focuses on giving users a solid foundation for organizing their lives. Automation and AI can be layered on top of that foundation without becoming requirements for using the product.
How I built it
LeveBase is built as a web-based Progressive Web App, with a focus on portability, offline usability, and a relatively lightweight architecture. The application uses vanilla JavaScript rather than a heavy frontend framework, with Cloudflare Workers and Cloudflare's platform services providing the backend infrastructure.
The architecture is designed around modular domains such as tasks, events, goals, notes, shopping lists, expenses, and journals. Authentication and authorization are handled separately from the application data, while access control and encryption are treated as first-class architectural concerns.
A major part of the ongoing architecture work is synchronization and interoperability. The goal is for LeveBase to work alongside services people already use rather than forcing them into a closed ecosystem. This includes planned bidirectional calendar synchronization and portable exports such as Markdown and HTML.
Challenges
The biggest challenge has been balancing breadth, simplicity, privacy, and maintainability.
A personal operating system can easily become an enormous application. Every additional feature creates new relationships, permissions, synchronization requirements, and edge cases. The challenge is therefore not simply deciding what can be built, but deciding what should belong in the core system.
Privacy creates another layer of complexity. Shared and personal data require different access models, and encryption has to account for those boundaries without making the application unusable.
LeveBase is still evolving, but the project has reinforced a central principle for me: a useful personal system should reduce cognitive overhead rather than create another source of it. The goal is to give people one connected place to manage life, while keeping their data understandable, portable, and under their control.
Log in or sign up for Devpost to join the conversation.