The first version of a Budibase app is usually plain: default theme, loose data model, and everyone an admin. That is fine for a proof of concept and risky for daily use. These ten customizations move your instance from “works” to “ours,” spanning theming, data modeling, access control, and operations hardening. Each one is a single conversation with the vibe-code agent on your OpenSysLab server, and each is small enough to review in minutes.

1. Theme the app to your brand

Default Budibase looks like default Budibase, and staff can feel that. The agent sets the app theme with your primary color, switches on dark mode where it fits, adds your logo, and renames the app to something your team will recognize. When the built-in options run out, it can inject custom CSS for the navigation bar and buttons. Branding matters even more if customers ever see one of your public forms. Try: “Apply my brand colors, add the company logo, and switch the app to a dark navigation bar.”

2. Harden the data model

Tables built in a hurry accumulate problems: free-text status fields, no relationships between tables, nothing marked required. The agent adds relationship columns linking Orders to Customers, constrains status to a fixed option list, sets required fields and sensible numeric ranges, and builds views on top for common slices like this year’s orders. Stronger structure pays back in every screen and automation you build later, because everything reads from the same clean definitions. Try: “Link Orders to Customers with a relationship, make status a fixed option list, require the order number, and add a view for this year’s orders.”

3. Split access by role

When everyone is an admin, everyone can break anything. The agent sets per-app roles, restricts sensitive screens to power users and admins, and builds role-filtered views so basic users only ever see their own rows. It then logs in as a basic test user to confirm the restrictions actually hold, because a permission that was never tested is a hope, not a control. Try: “Restrict the Payroll screen to admins, and make a view of the Deals table where each salesperson only sees their own rows.”

4. Restructure the navigation

Leftover screen names like “New Screen 1” confuse every new user and embarrass you in front of them. The agent renames screens to the words your team actually uses, groups them into sections like Operations and Reports, orders the menu to match how the work flows, and sets the landing screen. Ten minutes of navigation cleanup cuts onboarding questions for months. Try: “Rename the screens to plain English, group them under Operations and Reports, and make the Dashboard the home screen.”

5. Add custom JavaScript where the builder falls short

The builder covers most interface work, and for the rest Budibase lets you write JavaScript inside buttons and data bindings. The agent can add a button that runs a JavaScript action to recalculate totals on the fly, validate input before it saves, or compute a display field from several columns. It keeps each script small and explains what it does, so you are not left maintaining magic you never saw being written. Try: “On the Order screen, add a button that runs JavaScript to recalculate line-item totals and write the total back to the form.”

6. Move secrets into environment variables

API keys typed straight into a REST datasource configuration end up inside app exports, and exports travel further than you expect. The agent moves your keys into the server’s environment configuration and updates the datasource definitions to reference them, so exports are safe to share and a key rotates in exactly one place. It also lists any keys it finds sitting in plain text so nothing is missed. Try: “Move the API keys for my REST datasources into environment variables and update the configs to use them.”

7. Fix outgoing email identity

Automations that email customers or vendors should not arrive from a generic noreply address with the app name spelled wrong. The agent sets the from name and address, aligns the app display name that appears in the messages, and verifies delivery and spam scoring with a real test send to an outside mailbox. If mail was landing in junk, it adjusts the SMTP settings to your provider’s TLS port and retests. Try: “Make all Budibase emails come from ops@mycompany.com with my company name, and check that a test email does not hit spam.”

8. Build a staging copy for safe changes

Editing a live app that people depend on is how Fridays go wrong. The agent duplicates your production app into a staging copy pointed at a test datasource, so layout changes, new automations, and data model edits get tried there first and published to the real app only after you approve them. This one habit turns nervous tweaking into a normal process. Try: “Make a staging copy of my Orders app with its own test table, and walk me through how you would promote a change from staging to live.”

9. Tune performance before it hurts

The usual suspects behind a slow Budibase app are grids loading thousands of rows, heavy relationship columns on every screen, and attachments stored on container disk. The agent profiles the slow screens, adds pagination, points grids at filtered views that return less data, trims unneeded columns, and moves attachments to S3 or MinIO so they survive container restarts. Users notice screens that open in a second; nobody ever thanks you for a ten-second grid. Try: “My Jobs screen takes ten seconds to open — find out why, add pagination, and move attachments to S3.”

10. Put team login on SSO and audit the accounts

Password invites work for three users and rot by thirty. The agent configures OIDC single sign-on against your Google workspace or identity provider, restricts login to your domain, and then audits the existing accounts, flagging anyone inactive for 90 days so you can decide who to remove. Login becomes something your team already does every morning, and offboarding turns into disabling one directory account instead of hunting app passwords. Try: “Connect Budibase to my Google workspace SSO so only my domain can log in, and list accounts that have been inactive for 90 days.”

See it in action

Official walkthroughs from the Budibase team:

Worth a watch next:

• Components | Budibase University — how the building blocks of app screens fit together when you customize layouts.
• Views | Budibase V3 University — creating filtered custom views of your data, the technique behind several customizations here.

None of these are weekend projects; most take the agent minutes, and your review takes longer than the work itself. When you want Budibase shipped on a private server with the agent already inside, see Budibase on OpenSysLab.