Skip the blank canvas
Routing, tokens, and layout primitives are wired before you write a line of feature code.
Skip to main content
We get your Meta ads live within 28 days, with a system that filters out poor-fit leads, handles the chasing and shows you which ads bring in paying customers.
We get your Meta ads live within 28 days, with a system that filters out poor-fit leads, handles the chasing and shows you which ads bring in paying customers.
Setup
Full
Avg. Setup
28 Days
License
Commercial
We get your Meta ads live within 28 days, with a system that filters out poor-fit leads, handles the chasing and shows you which ads bring in paying customers.
We get your Meta ads live within 28 days, with a system that filters out poor-fit leads, handles the chasing and shows you which ads bring in paying customers.
Setup
Full
Avg. Setup
28 Days
License
Commercial
We get your Meta ads live within 28 days, with a system that filters out poor-fit leads, handles the chasing and shows you which ads bring in paying customers.
We get your Meta ads live within 28 days, with a system that filters out poor-fit leads, handles the chasing and shows you which ads bring in paying customers.
Setup
Full
Avg. Setup
28 Days
License
Commercial
Routing, tokens, and layout primitives are wired before you write a line of feature code.
Every component is a placeholder you can tear out the moment your real system arrives.
No proprietary abstractions, no hidden magic — just the conventions your team already uses.
Routing, tokens, and layout primitives are wired before you write a line of feature code.
Every component is a placeholder you can tear out the moment your real system arrives.
No proprietary abstractions, no hidden magic — just the conventions your team already uses.
Routing, tokens, and layout primitives are wired before you write a line of feature code.
Every component is a placeholder you can tear out the moment your real system arrives.
No proprietary abstractions, no hidden magic — just the conventions your team already uses.
Product teams reach for Frame when they need to skip the blank-canvas phase and get a working scaffold in front of stakeholders by end of week.
Product teams reach for Frame when they need to skip the blank-canvas phase and get a working scaffold in front of stakeholders by end of week.
Product teams reach for Frame when they need to skip the blank-canvas phase and get a working scaffold in front of stakeholders by end of week.
1
Pull the repo, install dependencies, and the dev server boots a working app on the first try — no setup steps, no missing env vars.
2
Replace copy, components, and tokens at your own pace. Each surface is intentionally generic so your brand drops in without resistance.
3
Routing and layout are already in place — point the templated views at your APIs and the structure carries the rest of the work.
4
Deploy on day one with a baseline that holds up to feedback, then evolve it as your product finds its real shape.
1
Pull the repo, install dependencies, and the dev server boots a working app on the first try — no setup steps, no missing env vars.
2
Replace copy, components, and tokens at your own pace. Each surface is intentionally generic so your brand drops in without resistance.
3
Routing and layout are already in place — point the templated views at your APIs and the structure carries the rest of the work.
4
Deploy on day one with a baseline that holds up to feedback, then evolve it as your product finds its real shape.
1
Pull the repo, install dependencies, and the dev server boots a working app on the first try — no setup steps, no missing env vars.
2
Replace copy, components, and tokens at your own pace. Each surface is intentionally generic so your brand drops in without resistance.
3
Routing and layout are already in place — point the templated views at your APIs and the structure carries the rest of the work.
4
Deploy on day one with a baseline that holds up to feedback, then evolve it as your product finds its real shape.
Frame let our team move from sketches to a working app on day one — by the time the brand system landed we were already iterating on real flows.
We tore out maybe a quarter of the components and the rest just stayed — the structure was right enough that nothing got in our way.
We brought stakeholders something tangible by Wednesday and shipped it the following week. Frame removed the part of the timeline we used to dread.
Frame let our team move from sketches to a working app on day one — by the time the brand system landed we were already iterating on real flows.
We tore out maybe a quarter of the components and the rest just stayed — the structure was right enough that nothing got in our way.
We brought stakeholders something tangible by Wednesday and shipped it the following week. Frame removed the part of the timeline we used to dread.
Frame let our team move from sketches to a working app on day one — by the time the brand system landed we were already iterating on real flows.
We tore out maybe a quarter of the components and the rest just stayed — the structure was right enough that nothing got in our way.
We brought stakeholders something tangible by Wednesday and shipped it the following week. Frame removed the part of the timeline we used to dread.
Each surface is intentionally generic so your brand drops in without resistance.
Each surface is intentionally generic so your brand drops in without resistance.
Each surface is intentionally generic so your brand drops in without resistance.
A small wall of work shipped on top of the template. Different fields, different aesthetics, same starting point.
Portfolio
Agency site
Product launch
Studio index
Newsletter
Conference site
Photo journal
Coffee shop
Music label
Restaurant
Gallery
Skate brand
Architecture
Type foundry
A small wall of work shipped on top of the template. Different fields, different aesthetics, same starting point.
Portfolio
Agency site
Product launch
Studio index
Newsletter
Conference site
Photo journal
Coffee shop
Music label
Restaurant
Gallery
Skate brand
Architecture
Type foundry
A small wall of work shipped on top of the template. Different fields, different aesthetics, same starting point.
Portfolio
Agency site
Product launch
Studio index
Newsletter
Conference site
Photo journal
Coffee shop
Music label
Restaurant
Gallery
Skate brand
Architecture
Type foundry
Start free, scale into the full library when your team is ready, and bring it in-house when the work demands it.
Save 20% with annual
For solo builders shipping their first version.
$0
/ month
Free forever
Wireframe template, single project use
Tokenized design system
Community support
Most popular
For teams who need every template, brand-ready on day one.
$24
$19.20
/ month
Billed monthly
Billed annually
Everything in Starter
Full template library access
Brand presets and theme tooling
Priority support, weekly updates
For organizations with bespoke design and compliance needs.
Custom
Volume pricing
Everything in Studio
Custom integrations and SSO
Dedicated solutions partner
Audit, SLA, and procurement support
Start free, scale into the full library when your team is ready, and bring it in-house when the work demands it.
Save 20% with annual
For solo builders shipping their first version.
$0
/ month
Free forever
Wireframe template, single project use
Tokenized design system
Community support
Most popular
For teams who need every template, brand-ready on day one.
$24
$19.20
/ month
Billed monthly
Billed annually
Everything in Starter
Full template library access
Brand presets and theme tooling
Priority support, weekly updates
For organizations with bespoke design and compliance needs.
Custom
Volume pricing
Everything in Studio
Custom integrations and SSO
Dedicated solutions partner
Audit, SLA, and procurement support
Start free, scale into the full library when your team is ready, and bring it in-house when the work demands it.
Save 20% with annual
For solo builders shipping their first version.
$0
/ month
Free forever
Wireframe template, single project use
Tokenized design system
Community support
Most popular
For teams who need every template, brand-ready on day one.
$24
$19.20
/ month
Billed monthly
Billed annually
Everything in Starter
Full template library access
Brand presets and theme tooling
Priority support, weekly updates
For organizations with bespoke design and compliance needs.
Custom
Volume pricing
Everything in Studio
Custom integrations and SSO
Dedicated solutions partner
Audit, SLA, and procurement support
Frame is a wireframe-stage scaffold for product teams. The repo boots a working app with routing, layout primitives, theming, and a set of intentionally generic component placeholders already in place — so the first feature you ship doesn't start from a blank canvas. Brand, content, and product details are meant to be overwritten at your own pace.
Clone the repo, install with your preferred package manager, and run the dev server. There's no install wizard, no setup script, and no required environment variables for the default routes. Most teams have a working local app within a few minutes.
Frame uses Next.js, Tailwind, and TypeScript out of the box, but it doesn't introduce custom abstractions on top of them. If your team already uses these tools, the conventions will look familiar. If you migrate off any one of them later, the rest of the scaffold is still useful.
Yes. Frame is licensed for unlimited commercial projects (you just can't resell the template itself), and intentionally easy to strip back to a minimal starting point. Teams use it as the first commit on internal tools, marketing sites, and early-stage product builds — anywhere the goal is to put structure in place before brand and copy land.
Theme tokens live in CSS variables and are wired through Tailwind's theme inline mapping. A floating theme switch toggles between light and dark; reduced-motion preferences and color-scheme metadata are honored automatically. Replace the token values with your brand palette and the rest of the system follows.
Frame intentionally omits anything that would couple it to a specific product: forms libraries, state managers, auth, analytics, and CMS integrations are not pre-wired. The structure is opinionated; the runtime behavior is not. Drop in whatever your team prefers.
That's the goal. Frame is meant to be torn out incrementally as your real design system, content model, and feature surface arrive. Most teams replace components piece by piece rather than all at once — by the time the scaffold is gone, the structure underneath has already paid for itself.
Frame is a wireframe-stage scaffold for product teams. The repo boots a working app with routing, layout primitives, theming, and a set of intentionally generic component placeholders already in place — so the first feature you ship doesn't start from a blank canvas. Brand, content, and product details are meant to be overwritten at your own pace.
Clone the repo, install with your preferred package manager, and run the dev server. There's no install wizard, no setup script, and no required environment variables for the default routes. Most teams have a working local app within a few minutes.
Frame uses Next.js, Tailwind, and TypeScript out of the box, but it doesn't introduce custom abstractions on top of them. If your team already uses these tools, the conventions will look familiar. If you migrate off any one of them later, the rest of the scaffold is still useful.
Yes. Frame is licensed for unlimited commercial projects (you just can't resell the template itself), and intentionally easy to strip back to a minimal starting point. Teams use it as the first commit on internal tools, marketing sites, and early-stage product builds — anywhere the goal is to put structure in place before brand and copy land.
Theme tokens live in CSS variables and are wired through Tailwind's theme inline mapping. A floating theme switch toggles between light and dark; reduced-motion preferences and color-scheme metadata are honored automatically. Replace the token values with your brand palette and the rest of the system follows.
Frame intentionally omits anything that would couple it to a specific product: forms libraries, state managers, auth, analytics, and CMS integrations are not pre-wired. The structure is opinionated; the runtime behavior is not. Drop in whatever your team prefers.
That's the goal. Frame is meant to be torn out incrementally as your real design system, content model, and feature surface arrive. Most teams replace components piece by piece rather than all at once — by the time the scaffold is gone, the structure underneath has already paid for itself.
Frame is a wireframe-stage scaffold for product teams. The repo boots a working app with routing, layout primitives, theming, and a set of intentionally generic component placeholders already in place — so the first feature you ship doesn't start from a blank canvas. Brand, content, and product details are meant to be overwritten at your own pace.
Clone the repo, install with your preferred package manager, and run the dev server. There's no install wizard, no setup script, and no required environment variables for the default routes. Most teams have a working local app within a few minutes.
Frame uses Next.js, Tailwind, and TypeScript out of the box, but it doesn't introduce custom abstractions on top of them. If your team already uses these tools, the conventions will look familiar. If you migrate off any one of them later, the rest of the scaffold is still useful.
Yes. Frame is licensed for unlimited commercial projects (you just can't resell the template itself), and intentionally easy to strip back to a minimal starting point. Teams use it as the first commit on internal tools, marketing sites, and early-stage product builds — anywhere the goal is to put structure in place before brand and copy land.
Theme tokens live in CSS variables and are wired through Tailwind's theme inline mapping. A floating theme switch toggles between light and dark; reduced-motion preferences and color-scheme metadata are honored automatically. Replace the token values with your brand palette and the rest of the system follows.
Frame intentionally omits anything that would couple it to a specific product: forms libraries, state managers, auth, analytics, and CMS integrations are not pre-wired. The structure is opinionated; the runtime behavior is not. Drop in whatever your team prefers.
That's the goal. Frame is meant to be torn out incrementally as your real design system, content model, and feature surface arrive. Most teams replace components piece by piece rather than all at once — by the time the scaffold is gone, the structure underneath has already paid for itself.