Websites had their WordPress moment. SaaS is having its BuildWithHQ moment. See the new BuildWithHQ homepage →
Home/Templates/Feature templates
Feature templates

Add one thing without rebuilding everything

Not every need is a whole application. Feature templates are the granular end of the library: one page, one component, one module, one data binding. They install into an application you already run and leave the rest of it untouched.

What you can install

Five granularities

See components in the console

Pages

A complete screen with its bindings and actions, dropped into your existing navigation.

Components

A reusable block — a chart, a panel, a specialized input — available to every page afterwards.

Modules

A new business object with its fields, validation, and relationships, inheriting the same permissions and logging as everything else.

Data connectors and bindings

Prepared wiring between components and data sources, so a new screen does not mean rewriting queries.

User types

A role shape with its menu, permissions, and default landing page defined together.

Why this matters commercially

The smallest sellable unit

Feature templates are where a lot of marketplace revenue comes from. A blueprint is a large purchase decision; a single well-made feature is an easy one.

If you have built something genuinely useful — a scheduling panel that handles a nasty edge case, an import wizard that actually validates, a reporting page a whole industry wants — that is a product. It does not need to be an application to be worth money.

Feature templates carry the same versioning, authorship, and validation as blueprints, so buyers can see who built it, what changed between versions, and whether it passed validation before listing.

Common questions

Questions about this

Will a feature template conflict with what I already built?

Installation is validated against your application first, and conflicts are surfaced before anything is written rather than discovered afterwards.

Can I uninstall one?

Yes, and installations are tracked as revisions so you can see exactly what was added and when.

Do feature templates get the same permissions treatment?

Yes. A module installed from a template goes through the same authorization path as one you defined by hand. There is no lesser tier.

Get started

Build it, then prove what it did

Create an account, explore the full builder console, and launch your first application on a custom domain. Nothing is charged while your application is still in development.

Start building today

No credit card required. The console preview, the documentation, and the architecture reference are all readable before you sign up.

Get started free Read the docs