FuseBase Sites

FuseBase Sites lets you build websites, landing pages, presentations, deal rooms and client portals. You manage a site by giving the AI agent plain-text instructions, by adding and editing blocks yourself, or by mixing both.

Portals follow a fixed structure with limited options for changing how they look and work. A site has no such structure, so you decide the design and the layout. Sites also work with FuseBase Apps, so a site can carry working features as well as content, and you can build most of it through AI.

No. Portals and Sites run side by side, and Portals are not being discontinued. Keep using Portals when their fixed structure suits your use case, and choose Sites when you need more freedom over appearance and functionality.

Yes. When you publish a site, you choose a subdomain on the FuseBase domain or add your own custom domain. One site can answer on up to three addresses.

By default anyone can, including anonymous visitors. In the Share settings you can require an email address, with or without validation through a magic link, and you can make each page public, unlisted or visible only to signed-in visitors.

It gives a client facing business one place for both halves of its work: the internal workspace where the team prepares, and the branded client portal where the client reads, approves and replies. FuseBase has been building for client facing teams since 2014.

Not unless you want them to. White labeling covers the portal itself, the domain it sits on and the address notifications come from, depending on what your plan and account type include. Check your own account for which of those are available to you.

They are stages of one process rather than two systems. The team prepares in the internal workspace, publishes what the client should see into the portal, and the client's reply or approval feeds the next internal step without anyone re-entering it.

Yes, within the permissions you set for it. An agent can prepare what a client asked for or keep a portal current, while a person reviews before the client sees it if that is how you configure it. You decide where the review step sits.