A Template, Not a Framework
The RAD Stack is a set of decisions — language, framework, database, deployment — made once so they do not get remade from scratch on every build. This template is where the application-level decisions become a repository: clone it, and the starting-point choices are already in place, wired together and building.
Where the Line Falls
The stack splits by lifecycle. Application choices change with every project: the router, the type-safe data access, the templating, the build pipeline, the test setup. What the host provides does not — so this template is written against a defined interface for the host, not against a specific implementation of one.
The RAD Stack Platform Template is the default implementation of that interface, pulled in by version rather than vendored into this repository. Nothing here requires it specifically — any implementation that satisfies the interface works, which is the actual point of drawing the line here rather than a way of avoiding a copy-paste.
What It Is Not
It is not a framework with its own abstractions to learn, and it is not a code generator producing something to then decode. It is exactly what My RAD Stack documents for the application layers, checked in and buildable — already assembled rather than described.
Status
Just starting development. The individual pieces have track records; the template itself is the next step — validating that the combination holds together as coherently as it holds apart.
If You Need More Than a Repository
This gets a team building on the stack; it does not teach a team why the decisions hold or how to apply them to a build the template did not anticipate. That is RAD Stack Adoption instead.
Want early access when it publishes, or need something like it sooner? Get in touch.