01
Clarity over magic
Conventions should save time without making the application impossible to understand. Generated code stays inspectable and the Vue model remains visible.
AboutRunable / Project
An independent open-source project exploring how productive Vue conventions can work with any backend.
A framework and a point of view
Good developer experience should expand your choices.
Runable is built around a simple belief: frontend productivity and backend freedom can belong in the same application.
The origin
01 / 03
Runable started with a practical frustration, not a plan to create another framework.
Vue made interface development enjoyable. Backend frameworks made complex server applications maintainable. Bringing both into one project still meant giving up the conventions of a modern Vue meta-framework or accepting a server runtime chosen elsewhere.
Runable began as an attempt to remove that trade-off. The project now focuses on a small application layer that connects Vue, Vite, routing, rendering, and data loading to the server already in place.
“The backend should be a deliberate architectural choice—not a side effect of the frontend tooling.”
How we build
02 / 03
Four principles guide the work.
02
Interoperability first
Runable should fit into an existing stack. It builds on open interfaces and works with the tools teams have already chosen.
03
Useful defaults
The common path should be fast and coherent. Advanced applications must still be able to replace, extend, or configure each layer.
04
Built in public
Decisions, experiments, and shortcomings belong in the open. Feedback from real projects is part of how the framework gets better.
Join the project
Runable grows through code, questions, experiments, and honest feedback.
Try it, report what feels rough, propose an API, improve the docs, or contribute a runtime adapter. Every useful contribution moves the project forward.