Why HTMQL

If you are evaluating whether HTMQL is the right tool for your project, this section is for you.

The problem HTMQL solves

Most web frameworks require you to learn a stack of libraries: an ORM, a routing convention, a templating language, a session library, a migration tool. Often you must first choose between several competing options for each. AI tools can write that code for you, but you still have to read it, debug it, and operate it.

HTMQL bundles these capabilities into a single server, and exposes them all through one interface you already know: SQL. The same query syntax that reads and writes your data also drives redirects, downloads, emails, and access control — no packages to install, no adapter code, no third-party documentation. Where the built-in approach doesn't fit, integrate any client-side JavaScript library or call external executables and scripts on the server.

Simple to run, no lock-in

Development is only the first chapter of a business application's life; most run for years. HTMQL is designed for that long second chapter:

One binary to operate. Updating the platform means replacing a single executable and restarting a service. There is no dependency tree to audit, no package ecosystem drifting out from under your application, no framework migration every eighteen months.
Plain text all the way down. Pages, templates, migrations, and configuration are readable text files. Backing up an application is copying a folder; putting it under version control takes one command.
No lock-in at any layer. Your data lives in a standard SQL database you control. Your .htmql files, templates, and migrations are feasible to convert to other platforms. The platform's source code is public under Apache 2.0. If the platform disappeared tomorrow, your application would keep running, and any developer could read exactly what it does.
No subscription. There is no per-user pricing, no metered tier, and no vendor who can reprice or retire the product your business depends on.

Who HTMQL is for

If you have ever been asked to build something like a Microsoft Access database but for the web - or found PowerApps and other low-code tools too limiting, too expensive, or too locked-in - HTMQL is designed for exactly that problem. It occupies the space between low-code platforms, which hide too much and often lock you into a subscription, and full web frameworks, which require a complete software stack. It gives you the productivity of a rapid development tool without surrendering control over your data, your code, or your deployment.

It is the tool for the one-person IT department, the business analyst who knows SQL, and the consultant who needs to deliver a working web app without building a full software stack.

HTMQL is a strong fit if you:

Know SQL and basic HTML but find modern web frameworks more complex than your problem warrants
Are building business tools, customer portals, reporting dashboards, or data entry applications
Want authentication, PDF, email, and file handling working out of the box
Want a simple deployment to Windows, Linux or macOS without Docker or other complex tools
Are connecting to a new or existing SQL database and want to build a web interface without an ORM layer between you and your data

When to choose something else

HTMQL is not the right tool for every project. Consider a general-purpose framework if you:

Are an experienced frontend developer who already has strong opinions about component frameworks, build pipelines, and state management - HTMQL's simplicity is a feature for some and a constraint for others
Are working in a team where multiple people need to specialize independently on frontend and backend
Are building a public API consumed by mobile clients or third-party integrations

For the large category of business applications that read from a database and present data to users - whether internal staff or external customers - HTMQL is designed to be the most direct path from a SQL schema to a working web application.