Field entry 01 · Web apps80+ ready-made components

Web apps, built by dragging.

Design real web apps, customer portals and internal tools. Link every part to your data, then publish to your own domain.

Get early access Read the docs

1,000 free tokens to try · Unlimited app users · Our cloud or your own servers

We open in waves. Join early access and we'll email you when your workspace is ready.

Fernleaf Supply/Storefront/Product page

DevProd Publish

FernleafShopTrailsStoriesHelp

Running

Trail Runner shoes

$129

Light, grippy and ready for wet rock. Built for long days on the trail.

ButtonPlace order

Drop a part here

Card

Best sellers {{ queries.getProducts.data }}

Ridge rain jacket$189

Summit pack 32L$149

Basecamp tent 2P$349

Published to Prod · fernleaf.app

Fig. 1. The web app builder at work on a Fernleaf Supply product page. Dev and Prod stages are on Team and Enterprise.

01What people build with itThree samples

Sites, portals and tools on one canvas.

The same builder makes the page your customers see and the screen your team works in. Here is what Fernleaf Supply made with it.

Web app

The Fernleaf gear site

Product pages that read straight from the products table, published on fernleaf.app.

Fig. 2.1 Trail Runner shoes, Ridge rain jacket and Summit pack 32L.

Customer portal

Where is my order?

Customers sign in and see their own orders, and nobody else's.

Fig. 2.2 Harshal checks order #10482.

Internal tool

The orders desk

Staff see orders over $500 waiting, approve them, and a workflow takes it from there.

Fig. 2.3 One big order waits for a manager.

02Build itEntries 01 to 03

Drag it. Bind it. Make it do things.

Three moves cover most of the work. Pick a part, point it at your data, then say what happens when people use it.

80⁺ready-made components in groups

Entry 01

Ready-made parts

Every page starts from parts you drag in. Layout, forms, tables, charts, menus and media are already built, so you spend the day on your app, not on the plumbing.

Layout, forms and inputs, date and time, capture and devices
Buttons and actions, navigation, overlays, feedback and status
Data display, media and embeds, text and code, charts and tables

Search 80+ components

Layout · a few of the parts in this group

Fig. 3. The parts rail. Pick a group to see some of what is in it.

{{ }}on any property

Entry 02

Bind to your data

Put {{ }} in any property and the part reads live values. A title, a price, a colour, whether a button shows. Your data sets it.

Data from a connection, a REST API, storage, messaging or static data
Or from an app action, a JavaScript query or a variable
Repeat a list with Loop in a part's Behavior tab: one copy per row

Data

Reads the products table in the Fernleaf database.

Result

Fig. 4. One property, eight places the value can come from. Pick one.

03events and actions

Entry 03

Make it do things

Each part has events. Pick one, then line up the actions that follow. It reads like a sentence, because it is one.

Events: click, change, submit, mount, visible and more
Actions: run a query, run a workflow, navigate, sign in, approvals
Set a variable, if / else, wait, show an alert and more

Event

Action

Then show an alert

Fig. 5. Build the sentence. The builder stores it as steps.

03Ship itEntries 04 to 07

Ready for the people who use it.

Visitors sign in, requests get approved, the look fits your brand, and every change goes live through a stage first.

04visitor sign-in

Entry 04

Sign-in for your visitors

Turn on the ways people may sign in to your app. Then decide what each person sees with app roles and access rules.

Email and password, magic link and Google on every plan
Team adds Microsoft, Azure AD, GitHub, GitLab, Apple, a phone code, anonymous sign-in and OpenID Connect. Enterprise adds LDAP or Active Directory
Multi-factor on Team and Enterprise, plus attack protection, bot checks and an audit log

Fernleaf

Sign in to your orders

Fig. 6. Switch a method on and the sign-in screen follows.

05approvals block

Entry 05

Approvals inside your apps

Drop an Approvals block on a page and people approve or reject requests right there, in the app they already use for work.

Requests come from your workflows
Approve or reject, and the workflow carries on
Show it only to the roles that decide

How approvals run in workflows

Approvals2 waiting

Order #10482Harshal · $612.50 · over $500
Restock Basecamp tent 2P$349 each · asked by the stock team

Fig. 7. The orders desk. Try approving one.

8built-in colour themes

Entry 06

Themes

Pick one of the built-in colour themes and every part follows it. Save a page as a template and start new pages from it instead of a blank canvas.

Save a page as a template, start new ones from it
Every part picks up the theme

Zinc theme, 1 of 8

Fig. 8. One page, eight themes. Pick a colour.

07stages and versions

Entry 07

Publish safely

Save a version and publish it. On Team and Enterprise, publish it to Dev first, try it with your team, then publish it to Prod. Something wrong? Go back to an earlier version.

Publish a saved version, and go back to an earlier one
More than one stage, like Dev and Prod Team and Enterprise
Compare two versions Team and Enterprise
Your own domain with a DNS checklist Team and Enterprise

Devv24your team tries it here

Prodv23fernleaf.app

Compare v23 and v24

+Card · Best sellers, loops over getProducts

~Place order · Click runs New order

Prod is on v23. Dev has one new version.

Fig. 9. Publish a version, then go back to the one before.

04Works withThe same data, every builder

Better with the other builders.

A page is where the rest of the workspace shows up. Charts sit next to forms, buttons start workflows, and tests replay what visitors do.

Connect pages to

PostgreSQLMySQLSQL ServerOracleMongoDBFirebaseREST APIsGoogle SheetsStripeSlack

Sign visitors in with · Google on every plan, more on Team, LDAP on Enterprise

GoogleMicrosoftAzure ADGitHubGitLabAppleOpenID ConnectLDAP or Active Directory

And more. The list grows with every release. See all integrations

05Plan notesWhat changes by plan

The fine print, in plain words.

What depends on your plan, and what does not, for web apps.

See pricing

People who use your published apps: Unlimited on every plan
Your own domain, with a DNS checklist Team and Enterprise: Team is $99 a month
Live cursors and co-editing: Team and Enterprise
More than one stage per app, and compare versions: Team and Enterprise
App roles, access rules and multi-factor: Team and Enterprise
Visitor sign-in methods: Email, magic link and Google on every plan. More on Team. LDAP on Enterprise
Where it runs: Our cloud or your servers, every plan
How you pay: Starter buys tokens up front. Team is $99 a month. Enterprise is a yearly contract

What a public site costs

Pay when people visit, not per person.

0.04: token for a public page visit. One charge for the whole page, up to 5 charts. 10,000 visits is 400 tokens, about $5 on Team. Bots are filtered out before counting.
0.04: token for a public search. Suggestions while typing are counted once, with the search. 1,000 searches is 40 tokens, about $0.50 on Team.
1: token a month for every 100 rows you keep. 10,000 rows is 100 tokens. No cap on items.
$99: a month is Team, the plan for your own domain. All of it becomes tokens.

Unlimited app users on every plan. A daily spend cap keeps the bill from running away.

What a public site built here can do

One tool, and one bill.

Live data from your database. Pages read straight from your tables.
Charts on the site. Put a chart next to your text.
Member pages. Each person sees only their own rows.
Forms that save to a real database. No copy and paste in between.
Automatic tasks built in. Emails and nightly jobs run from the same place.
One bill for the site, the data and the tasks.

06Questions

Fair questions.

Yes, on Team ($99 a month) and Enterprise. Add your domain in the app's Domains settings, set the records the DNS checklist shows, then upload your own certificate.

No. People who use your published apps are unlimited on every plan. Seats are for the people who build in your workspace.

Yes. Email and password, magic link and Google come with every plan. Team adds more, like Microsoft, GitHub and OpenID Connect, and Enterprise adds LDAP. App roles and access rules, on Team and Enterprise, decide what each person sees.

A public page visit costs 0.04 token for the whole page, and a public search costs 0.04 token with typing counted once. 10,000 visits is about $5 on Team. Rows you keep cost 1 token for every 100 a month, with no cap on items.

Yes, with JavaScript queries. Write the logic in JavaScript, then bind its result to any part with {{ }}.

Where to begin

Build your first page.

Drag in a few parts, bind them to a table, and publish to Dev before lunch.

Get early access Talk to us