Marketing and customer sites without code

Builder Sites generates any project that loads in a browser, such as a marketing site, a dashboard, a client portal, a docs site, a SaaS interface, or a single-page form, from a description that you write.

Get early accessView all products

Any site that opens in a browser

Builder Sites builds any project that opens in a web browser. When you describe a landing page, a customer dashboard, a documentation site, or a full SaaS interface, Beryl Agents generate its pages, layout, data connections, and deployment settings. You can then review the site in a live preview, adjust it, and publish it. Your marketing team can publish its own campaign pages, while your operations team sets up its own internal dashboards.

Launch any browser-based project by describing it

Builder Sites builds marketing pages, client dashboards, documentation sites, and SaaS interfaces in one editor. The steps below follow a site from your description to its published URL.

What Builder Sites builds and hosts for you

From a description to a live preview illustration

From a description to a live preview

If you build a page by hand, you will have to drag each element into place, set up the layout, connect the data, and test the result at every screen width. A stakeholder can see the page only after that last step.

From your description, Beryl Agents generate the pages, the navigation, the responsive layout, and the content structure of the site. Builder opens the result in a live preview as soon as generation finishes, so you can review it, ask for changes in plain language, or edit it directly.

Hosting and SSL set up when you publish illustration

Hosting and SSL set up when you publish

Once you build a site, you will still have to set up hosting, install an SSL certificate, connect a domain, and manage each deployment. If your team has no one who manages servers, you will have to find someone who does before the site can go live.

Delalify hosts every Builder site on a managed runtime. When you publish, Builder serves the site on a default URL straight away. You can then connect a custom domain to it whenever you are ready. Builder provisions the SSL certificate for each domain, while Delalify scales the site and keeps it online.

Dynamic data from Tables and People illustration

Dynamic data from Tables and People

Static pages suit marketing copy; however, once you add product listings, a team directory, an event calendar, or a dashboard for each customer, you will have to rebuild the site in code or update its content by hand.

Builder Sites can show live data from Tables for listings, directories, and dashboards, and from People for pages about your contacts. When someone adds a row to the listings database, a property listing site shows the new property straight away. A team directory updates in the same way when someone changes a colleague's details in People. Each data connection is optional, so a static site works too.

Responsive across every screen size

Any visitor can open your site on a phone. If the tool that you build with produces desktop layouts, you will have to rebuild each layout by hand for every screen size.

Beryl Agents build a responsive layout into the first version of every site, so each page fits desktop, tablet, and phone screens from the start. You can preview the site at each screen size in the editor before you publish it.

Forms that feed your workflow illustration

Forms that feed your workflow

A separate form tool will usually save each submission to a spreadsheet or send it to an email inbox. Someone on your team will then have to turn each submission into a contact record, a notification, or an approval request, with another tool for each.

Any Builder site can include a form that saves each submission as a People contact, starts a workflow in Builder Workflows, or writes a row to Tables. A lead capture form, for example, can create the contact, tag it, assign an owner, and send a welcome email through Channels, because Builder connects the form to those products for you.

Client portals with access control illustration

Client portals with access control

A client portal has to show each customer the records that belong to that customer alone. If your tool charges for each user, you will pay for a seat for every client that you invite to the portal. If you email spreadsheets to avoid that bill, you will give up the access control with it.

Builder Sites can use Teams access control to set what each user can see, so each client opens their own projects, invoices, and files after logging in. Because each client signs in as a People contact, not as a billable seat, a portal for hundreds of clients adds no seats to your bill.

Why teams build their sites in one editor

Publish pages yourself

Your team reviews each page in the live preview and publishes it from Builder, so you decide when a campaign page or an internal dashboard goes live.

One tool for every browser-based project

Your team builds landing pages, documentation, dashboards, SaaS interfaces, and client portals in the same editor, so it learns one set of steps for every kind of site.

Live data only where a page uses it

A simple marketing page can work with no data connection at all, while a customer dashboard shows live data from Tables and a client portal limits access through Teams. You add only the connections that each project uses.

Hosting that Delalify manages

Delalify manages the servers, the SSL certificates, and the scaling behind every site, so your team's last step is to publish it.

How teams use Builder Sites

A marketing lead builds a product launch page from a description

The marketing lead describes a launch page with a hero section, feature highlights, a pricing table, and an email signup form. Builder generates the page with a signup form that saves each new signup as a People contact tagged Product Launch. The team reviews the page, adjusts the copy, and publishes it.

Result

A workflow connected to the Product Launch tag starts the follow-up email sequence for every contact that the form tags. The marketing lead publishes the page from Builder, so they no longer have to book time in the design and engineering queue.

A marketing lead builds a product launch page from a description

Bookkeeping firm gives 60 clients a private financial portal

A small bookkeeping firm emails monthly reports, tax documents, and invoices to 60 clients and loses track of which client opens which file. A partner describes a client portal with a financial summary page, a document vault for statements, and an invoice history. With Teams access control, each client's login opens that client's own books.

Result

Each client finds last month's statement in the portal, so the firm no longer attaches sensitive documents to outgoing email. Because every client signs in as a People contact, the firm pays for the same number of seats as it takes on new clients.

Bookkeeping firm gives 60 clients a private financial portal

A developer relations team edits its docs as rows in Tables

The developer relations team needs API documentation with versioned pages, code examples, and search. The team describes the structure to Builder: sidebar navigation grouped by product area, code blocks with syntax highlighting, and a search bar. The site loads its content from a Tables database, so authors update the docs by editing rows.

Result

An author publishes a change to the docs by editing its row in Tables, so the developer relations team no longer has to wait for an engineering deploy. The team can therefore update the docs on the day that engineering releases each API version.

Cooking studio takes class bookings and payments on one page

Saffron Lane holds evening cooking classes and takes bookings over the phone in a paper diary. The owner describes a booking page with a schedule of upcoming classes, seat selection, payment through Wallet, and a confirmation that Channels sends with the address. The owner publishes the page from Builder on the studio's own domain.

Result

Students book and pay for a class on the page at any hour, while Builder saves each of them as a People contact for the studio's newsletter. The owner checks each evening's class list on the page, so they no longer count entries in a paper diary.

Cooking studio takes class bookings and payments on one page

Explore more of Builder

Apps

Builder generates native apps that install on a device and keep working offline.

Learn more

Workflows

Drag triggers, branches, and approval steps onto a canvas to set what your Builder app does after each event.

Learn more

Components

Start each Builder project from ready-made blocks, a full template, or components from the gallery.

Learn more
View all Builder features

Build any site by describing it

Request early access, then describe your first marketing page, dashboard, or client portal and publish it to a managed runtime.

Get early accessView all products