FAQs
What is Buzzy?
Buzzy is a low-code/no-code app platform for creating web and mobile applications from a structured app definition. You can start with a prompt, a Figma design, Builder MCP, or direct no-code Workspace editing.
A Buzzy app definition can include brief, flows, data model, blueprint, theme, screens, functions, widgets, people, settings, tests, security configuration, APIs, and MCP exposure.
How is Buzzy different from AI tools that generate code?
Many AI app tools generate a new codebase for each app. That can be fast at first, but it leaves you responsible for understanding, hosting, upgrading, securing, and maintaining the generated code.
Buzzy uses AI to help create or edit a structured app definition. The Buzzy runtime renders that definition into working web and mobile apps. This is the difference highlighted across the Buzzy blog: the long-term value is not just generating something quickly; it is keeping the app editable, testable, governable, and maintainable after launch.
Related reading:
What are the main ways to create an app with Buzzy?
There are four common starting points:
You want a first version from a prompt.
You have a design file or design-led workflow.
You want an AI coding agent to build, adapt, inspect, or change the app in stages.
No-code Workspace editing
You want to edit the app directly in Buzzy.
All four paths work with the same app model. You can start with one and continue with another.
Can I start with Buzzy AI and keep editing later?
Yes. A prompt-generated app is a starting point. After generation, continue in the Workspace:
refine the brief and flows
adjust datatables, fields, relationships, and permissions
update blueprint and screens
edit the theme
add functions, constants, widgets, APIs, or MCP
configure People, Teams, Organizations, and Settings
add Tests and run Security Review
See Buzzy AI and The Building Blocks.
Can I start with Figma?
Yes. Use Buzzy for Figma when the design file is the starting point. The Buzzy Figma plugin can turn marked-up Figma screens into a working Buzzy app with real data, forms, navigation, and responsive layouts.
You can also start with Buzzy AI, then refine the app in Figma.
What is Builder MCP?
Buzzy Builder MCP lets an AI coding agent such as Codex or Claude Code work with Buzzy as a structured app builder. The agent can inspect and update app artifacts such as brief, flows, data model, theme, blueprint, screens, functions, widgets, and settings.
Builder MCP is useful for staged app creation, adapting templates, adding code widgets, creating Buzzy Functions, fixing screens, validating changes, and preparing reviewable pull requests.
What is Buzzy Custom MCP?
Buzzy Custom MCP exposes an existing Buzzy app to MCP clients such as ChatGPT or Claude. It is app-specific: the assistant can use governed tools generated from that app's datatables, functions, widgets, and permissions.
Use Builder MCP to build or edit an app. Use Custom MCP after an app exists and you want an assistant to work with that app's data and actions.
Can I still build manually without AI?
Yes. You can use the Buzzy Workspace directly to work with Data, Design, Theme, Constants, MCP, Functions, People, Settings, Publish, Tests, Security, and Versions.
AI is a useful accelerator, not a requirement for every change.
Can I use custom code?
Yes, but use the smallest extension point that fits the job:
Code widgets for custom UI inside screens.
Buzzy Functions & Constants for server-side logic, secrets, AI calls, webhooks, and external APIs.
REST API Reference for external systems.
Buzzy Custom MCP for assistant-facing app tools.
Use API and Extension Surfaces to choose the right surface.
Can Buzzy integrate with other systems?
Yes. Buzzy supports REST API access, Buzzy Functions, constants, code widgets, datatable rules, imports from CSV or URLs, and MCP. Integrations should authenticate as the correct user or integration account and respect row access, field access, and Private Data rules.
See Buzzy REST API, Buzzy Functions & Constants, and API and Extension Surfaces.
How does Buzzy handle security?
Buzzy security is layered:
app privacy and authentication
app roles such as Admin, Author, and Audience
People, Teams, and Organizations
datatable row access
field view and field edit
Private Data classification, masking, reveal, encryption, and audit behavior
API and MCP governance
deployment controls for production and enterprise environments
See Security and Access Control, Private Data, and Security Review.
How should I test a Buzzy app?
Use Tests for repeatable smoke and regression checks. Good candidates include login, onboarding, main CRUD paths, search and filter, approvals, bookings, payments, admin flows, permission-sensitive paths, functions, widgets, APIs, and MCP-backed behavior.
Use the In-App Debugging when a screen binding, form, view, action, filter, or row context is not behaving correctly.
Can Buzzy create native mobile apps?
Yes. Buzzy can support web and native mobile app delivery depending on your plan and deployment setup. Native app publishing requires the appropriate Buzzy deployment and app store preparation.
See Buzzy Deployment & App Stores, iOS & Android App Deployment, and Apple & Google App Stores.
Does Buzzy support offline mobile use?
Buzzy's mobile architecture can support offline-first use cases where app design and app data are available on-device and changes sync back when connectivity returns. Offline behavior, conflict handling, and offline maps depend on app requirements and deployment configuration.
For complex offline workflows, plan and test the data model, sync behavior, conflict scenarios, file/image handling, and user permissions early.
Do I need a deployment plan?
For design, prototyping, and early testing, you may be able to work on app.buzzy.buzz. For production apps, custom domains, customer-facing deployments, native mobile apps, single-tenant infrastructure, or enterprise requirements, you need an appropriate deployment plan.
See Buzzy Deployment & App Stores and Publish your app to your Deployment.
Can I self-host Buzzy?
Enterprise deployment options can support customer-controlled infrastructure such as private cloud or on-premise environments. See Introduction to deployment and contact Buzzy to discuss requirements.
Can I access the database directly?
Buzzy uses MongoDB underneath Buzzy deployments. For most integrations, use Buzzy's REST API, functions, exports, or MCP surfaces rather than writing directly to the database. This helps preserve Buzzy's data integrity, permissions, and runtime behavior.
Do I get the Buzzy runtime source code?
No. The maintained Buzzy runtime is part of the platform. Your app definition, Figma design assets, functions, constants, widgets, data model, and configuration are the app-specific assets you control. This is what allows Buzzy to keep improving the runtime without forcing every customer to maintain a forked application codebase.
How do I choose between Buzzy AI, Figma, Builder MCP, and no-code editing?
Start with What to Use When. In short:
choose Buzzy AI for fast first drafts
choose Figma for design-led creation or visual iteration
choose Builder MCP for staged AI-agent builds and deeper changes
choose no-code Workspace editing for direct app maintenance
Where can I get help?
Use:
Buzzy Accreditation for partner and implementation skill validation
Buzzy blog for current thinking, product examples, and AI app delivery guidance
Last updated