Create sites, apps, and workflows without writing code

When you describe a site, a mobile app, or an internal tool in plain language, Beryl Agents generate its pages, data connections, and workflows, so your team can publish it without writing code.

Get early accessView all products

Describe it, then publish it

Builder generates a working site or app from a written description of what you need. Beryl Agents write the pages, the database, the workflows, and the deployment settings, which you can review and adjust before you publish. When the app needs contacts, messages, files, permissions, data, or payments, it can use People, Channels, OneCloud, Teams, Tables, and Wallet, because Builder connects to them inside your Delalify workspace with no third-party integration to set up. The person who needs an internal tool can describe it, review the preview, and publish it in Builder on their own.

Describe what you need and put it in front of your users

Builder generates a working site, mobile app, or internal tool from a plain-language description. The steps below show how your team reviews that project, connects it to the rest of Delalify, and publishes it.

What Builder generates from a description

Sites and apps generated from a description

If you build with a drag-and-drop editor, you will have to place each element, connect each data source, and fix each layout problem yourself. An AI code generator saves that work, but someone on your team will then have to deploy, host, and maintain the code that it writes.

When you describe what you want in plain language, Beryl Agents generate the whole project, including its pages, components, data connections, and deployment settings. You can review the result in a live preview and ask for changes in the conversation or edit the project directly before you publish it. Delalify hosts each published project on a managed runtime, with an SSL certificate and automatic scaling from the first publish.

One editor for every kind of site

Your marketing team may need landing pages, while your support team needs a docs site and your sales team needs a client portal. If each team builds its site in a different tool, every team will have to learn a separate editor, login, and publishing process.

Builder can produce any project that loads in a browser, such as a marketing site, a portfolio, a blog, a documentation site, a dashboard, an admin panel, a SaaS interface, or a single-page form. Every project uses the same editor, the same components, and the same publishing steps, so your team learns one tool for all of them.

Native apps for iOS, Android, and desktop

If you build a mobile app by hand, you may need specialists for each platform, a separate codebase for iOS and for Android, and a release plan for each app store. Because of that cost, an organization can end up keeping an internal tool in the browser alone.

Builder generates native apps that install on a device and keep working offline. From one description, Beryl Agents produce an iOS app and an Android app, along with a desktop app for macOS, Windows, or Linux if you want one. Beryl Agents also take care of each platform's conventions, so your team only has to decide what the app does.

Visual workflows for in-app logic

An app usually needs backend logic for what happens when a user submits a form, when a customer places an order, or when a renewal date comes due. If your tool allows one trigger per automation, you will have to call a developer as soon as that logic needs to branch.

Builder Workflows gives your app a visual backend, which you build by dragging triggers, conditions, branches, loops, and approval pauses onto a canvas and setting up each one. When a user submits a form, for example, a workflow can send a notification, create a record, pause for a manager's approval, and then grant access. Workflows execute on a durable pipeline engine, which saves the result of each step so that it can resume a workflow after a crash. The engine also retries any step that fails and records every run in an audit trail.

Reusable components and templates illustration

Reusable components and templates

Before you can work on the parts of a project that are specific to your organization, you will have to build a login form, a navigation bar, a dashboard layout, and, for a store, a checkout flow. If you build those from scratch, you will repeat the same work at the start of every project.

Builder includes ready-made components for common patterns, such as authentication forms, navigation layouts, data tables, checkout flows, file upload areas, and admin dashboards. For a SaaS app, a client portal, an event site, or an internal tool, you can start from a project template, which is a working app with those pieces already in place. Either way, you can drag in more components and customize each one.

0

Lines of code required

1

Tool for sites, apps, and workflows

0

Third-party integrations to link

Why teams build their own tools with Builder

Teams publish their own projects

Your marketing, sales, support, and operations teams can describe what they need and publish it themselves, so your engineers can keep working on your core product.

Contacts, messages, files, and permissions built in

A Builder app can find contacts in People, send messages through Channels, save files to OneCloud, and apply access rules from Teams, with no third-party service to configure. Every connection is optional, so you switch on only the ones that your app uses.

Browser, mobile, and desktop from the same tool

Builder produces sites for the browser, apps for iOS and Android, and apps for desktop computers from the same editor, so your team learns one tool to reach users on each of those platforms.

Backend logic without code

You define in a workflow what your app does after each form submission, order, or event. The pipeline engine retries a step when a connection drops, so each workflow completes. For a sensitive action, you can add an approval step that pauses the workflow until the person whom you name approves it.

How organizations use Builder

A school's admissions office launches an enrollment portal

The admissions office describes an enrollment portal for parents, with an application form, a document upload, tuition payment, and status tracking. Builder generates the site and connects it to People for applicant records, OneCloud for documents, Wallet for tuition payments, and Channels for status updates. The admissions team reviews the preview and then publishes the portal from Builder.

Result

Parents fill in the application, upload transcripts, and pay the deposit on the same site, which saves each applicant's record to People and each document to OneCloud. The admissions staff review every application from that record, so they no longer chase paper enrollment packets.

A school's admissions office launches an enrollment portal

Solo designer who needs clients to approve work in one place

A solo designer wants clients to see project milestones, approve deliverables, and download final files. The designer describes the app to Builder as a dashboard for each client, which lists active projects with an approval button on each deliverable and a section for downloads. The generated app keeps the files in OneCloud and uses a workflow that notifies the designer through Channels when a client approves a milestone.

Result

Each client approves milestones and downloads files from their own dashboard, while Channels notifies the designer of every approval. The designer tracks each project's sign-offs in one place, so they no longer search email threads for them.

Operations team replacing a shared spreadsheet

An operations team tracks 400 vendor relationships in a spreadsheet with 30 columns, broken formulas, and three conflicting copies. The team describes an internal vendor tool to Builder, with a searchable directory, a renewal alert 60 days before each contract expires, and a review workflow that sends each expiring contract to the procurement manager. The app stores the vendor data in Tables, while a Builder workflow sends the renewal alerts.

Result

Every vendor record is in one Tables database, so the team no longer emails copies of the spreadsheet to one another. The procurement manager approves each renewal from a queue that the workflow fills 60 days before the contract expires.

Operations team replacing a shared spreadsheet

Brokerage that wants buyers to browse listings and book viewings

A brokerage needs a public listing site where buyers can browse properties, filter by neighborhood and price, book viewings, and receive alerts about new matches. The marketing coordinator describes the site to Builder, which generates a site that shows listings from Tables, saves each buyer inquiry as a People contact, and sends viewing confirmations through Channels.

Result

The site shows each new listing as soon as an agent adds it to Tables, so the coordinator publishes no listing pages by hand. The sales team works through buyer inquiries from their People contacts, which means that the team no longer sorts them in a shared inbox.

Brokerage that wants buyers to browse listings and book viewings

Youth sports league collecting waivers before each season

Coral Coast Soccer registers 900 players every spring and spends weeks of each season collecting signed waivers and medical release forms. The league director describes the registration flow to Builder: a registration form that works on phones, an upload to OneCloud for proof of insurance, a consent step for the liability waiver, and a workflow that creates the player record in People and notifies the team coordinator through Channels once a registration is complete.

Result

The form accepts a registration only with the signed waiver and the medical release attached, so the team coordinator receives a notification for complete registrations alone. The workflow attaches each medical release to the player's record, where a coach can open it on game day.

Youth sports league collecting waivers before each season

What Beryl does in each Builder project

Beryl Agents generate each project from your description, after which Beryl can sort workflow data and suggest components as your team builds.

AI-generated projects

Beryl Agents generate the pages, components, data connections, and deployment settings for a site or app from a plain-language description of it.

Learn more

Help inside your workflows

Beryl sorts incoming data into categories, routes each approval to the right person, and suggests changes to a workflow from the record of its past runs.

Learn more

Component recommendations

Beryl suggests components and templates from the gallery that fit your project description and the patterns that your project already uses.

Learn more
Explore Beryl for Builder

All supported integrations

Connect Delalify People with the tools your team relies on. Sync data automatically and keep everything current across your entire workflow.

Salesforce

Sync accounts, deals, and customer journeys.

HubSpot

Connect marketing campaigns and sales pipelines.

Google Workspace

Integrate Gmail, Drive, and Calendar.

Microsoft 365

Connect Outlook, Teams, and Exchange.

Slack

Push contact updates to team channels.

Zoom

Log meetings and surface call history.

WhatsApp

Send messages and engage contacts directly.

LinkedIn

Connect professional networks and contacts.

Facebook

Reach audiences through social campaigns.

X

Sync your followers and track engagement.

Blackbaud

Sync donor records and fundraising campaigns.

Canvas

Connect student data and course information.

Zendesk

Unify support tickets and customer context.

DocuSign

Manage agreements and consent forms securely.

Zapier

Connect 6,000+ apps without code.

Shopify

Sync customers, orders, and store data.

Stripe

Connect payment data and customer profiles.

Mailchimp

Sync audiences and automate email campaigns.

Intercom

Unify conversations and customer messaging.

API

Build custom integrations securely.

Explore Builder in more detail

Each page below covers one part of Builder: sites for the browser, native apps, backend workflows, and reusable components.

Sites

Builder generates marketing sites, dashboards, client portals, and SaaS interfaces from your description.

Explore

Apps

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

Explore

Workflows

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

Explore

Components

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

Explore

Common questions about Builder

Build your next site or app from a description

Builder connects each project to Tables for its data, Wallet for its payments, and Beryl for the agents that generate it.

Get early accessView all products