> For the complete documentation index, see [llms.txt](https://docs.lingoql.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lingoql.com/sub0/introduction.md). # Introduction Sub0 is a backend construction engine for defining data models, business logic, policies, and interfaces without framework and boilerplate overhead. Sub0 is the backend construction engine behind LingoQL. It helps teams define data models, business logic, policies, and interfaces without rebuilding the same backend stack for every project. ![sub0.lingoql.com image](https://cdn.hashnode.com/res/hashnode/image/upload/v1768811304409/8d8e7602-1106-4f0d-98e1-a341c4bb0a82.png) ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1768811361666/985c42f3-d1cc-4806-b0bb-6ffe4e31add1.png) ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1768811572754/7bd42c89-1082-418f-88ee-1fb15ae8c0bc.png) ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1766246556354/9c0fc862-df9f-457a-b658-e11acb77f69b.png) ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1766246837876/a2c1d17e-cc8b-43f4-a0da-a58ad2be4c95.png) Sub0 replaces boilerplate setup with a pre-compiled execution model. You focus on intent, not framework assembly. That means less time spent on dependencies, ORM setup, folder structure, and deployment assumptions. Teams can move from idea to production-ready backend services much faster. Sub0 is language-agnostic and optimized for fast iteration, predictable behavior, and production safety. *** ### Why Sub0 Exists Modern backend development is powerful, but often too heavy. Even simple backends usually require teams to: * Pick and learn a programming language and framework * Decide on architectural patterns upfront * Configure dependency management and build tooling * Set up ORMs, migrations, and data access layers * Define folder structures and conventions * Rebuild the same glue code across projects * Re-solve deployment and environment concerns Sub0 removes that repetition with a standardized, execution-ready backend foundation. *** ### What Sub0 Solves #### 1. Less language and framework churn With Sub0, you do not need to: * Learn a new programming language just to ship a backend * Re-evaluate frameworks on every project * Rewrite the same logic across different stacks Sub0 uses one backend execution model across projects. *** #### 2. Less dependency and framework management Sub0 removes the need to: * Manage package managers * Resolve version conflicts * Maintain fragile dependency graphs * Patch security vulnerabilities across libraries You build against a stable runtime surface. *** #### 3. Less ORM and data layer boilerplate Sub0 reduces: * ORM setup and configuration * Query builder decisions * Schema-to-code impedance mismatch * Repetitive CRUD scaffolding Data access stays explicit and predictable. *** #### 4. Less project setup overhead You spend less time on: * Repo structure debates * Repeating the same folder layouts * Bootstrapping config-heavy projects Sub0 starts with working structure by default. *** #### 5. Faster time to production Because Sub0 standardizes execution, structure, and behavior: * Prototypes become production systems * MVPs don’t require rewrites * Teams ship earlier with fewer engineers * Systems remain maintainable as they scale * Deploying a Sub0 app typically takes **15–22 seconds** *** ### The Sub0 Philosophy Sub0 is built on a simple belief: > **Backend development should be about expressing intent, not assembling infrastructure.** By lowering the abstraction level of *backend construction* (not capability), Sub0 enables: * Faster development cycles * Fewer architectural mistakes * Lower long-term maintenance costs * More predictable systems *** ### In One Sentence > **Sub0 is a backend construction engine that removes boilerplate, reduces cognitive load, and lets teams build production-grade backend services at lightning speed.** Next, see [Getting Started](/sub0/getting-started.md) to create your first Sub0 project. For more background, read the [Sub0 White Paper](https://drive.google.com/file/d/1rG9VBGadGbyGHJY9BgNiOzpDLUbscmub). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.lingoql.com/sub0/introduction.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.