Do I need to choose a deployment plan if I'm just designing/creating/testing an app or site? 
No, our Buzzy Creator licenses may be all you ever need. These licenses are for working in Figma with your colleagues, collaborating on designs and testing each app/site with up to 5 Test Users.

​

If I want to test with more than 5 Test Users (or real end-users), what do I need? 

You’ll need one of the “Deployment” options. Which one depends on what you’re trying to do, and how many users you anticipate.

​

 The “Small” deployment option looks great, but how many users will it handle, and can I use it in production? 

The “Small” deployment is great if you have a web-only deployment and want to test with a small number of users. Based on your requirements, this may be fine for production. The database is shared, so its performance will be dependent on what’s happening on the server at that point in time. This type of deployment is great for small user cohorts, usability testing, concept validation and so on.

​

Can I start with "Small" and move up to the next level? 

Yes, you can migrate up. Migrating down is more complicated and requires support to ensure you are not losing data - contact us.

​

How do I know what size Buzzy Deployment server I need? 

This depends on the specific application and factors like user concurrency levels, transaction rates etc. As per any software solution, sizing should be taken into consideration when planning and designing your system. Our Large + Advanced Features are aimed at providing you a flexible and cost effective way of providing a performant solution for your customers.

​

What data-center regions do you support? 

Currently we run in 3 regions: the United States, the EU and APAC (Sydney). For additional region support under our Enterprise plan, please contact us to discuss.

​

Can we self-host? 

Yes, this falls into our Enterprise plan, please contact us.

​

How do I get my Buzzy app into our own Apple or Google (Play) store? 

During the setup process, we’ll coordinate with your team to connect our automated system to enable the relevant app store publishing.

​

Do you support corporate MDM for app publishing? 

Yes, this is done under our Enterprise plan, please contact us to discuss.

​

Is Buzzy secured? Do you support standards like GDPR, HIPAA etc? 

The Buzzy development team follows best practices to deliver enterprise grade software. We employ regular security scanning software to help identify and fix ever changing security requirements. For compliance standards like GDPR and HIPAA it will be a mix of you our customer following those protocols to ensure support alongside our underlying capabilities.

​

What is the database underneath Buzzy and do I get access to it?
Buzzy uses MongoDB under the covers, which has incredible ability to scale and deal with complex data.  Each Buzzy server gets its own MongoDB cluster, and yes, you can get access to it, however we recommend getting your data from the Buzzy REST API to ensure you maintain data integrity.

​

How does Buzzy scale?

Buzzy’s server and client architecture is built on best-of-breed technology. Each Buzzy deployment is single-tenant, meaning you get your own compute units, database cluster and S3 compatible storage.

 

Our servers are deployed on Kubernetes (k8s) infrastructure. This means that the applications can be configured to scale horizontally and vertically for robustness/reliability and performance.

 

As every application’s performance requirements are different, when you choose a deployment plan (eg Large) that has multiple compute units, you can optionally configure these compute units to meet your requirements. For example, you may use a web cluster, mobile cluster, end user cluster, admin user cluster, worker servers for API access etc.

 

Our database is MongoDB and we use our leading service providers MongoDB Atlas and Digital Ocean, so it’s rock solid, best-of-breed infrastructure. Each Buzzy deployment has its own MongoDB cluster, which is deployed either in shared infrastructure or on dedicated clusters, depending on the plan you choose. 

 

Our mobile technology is React Native, with SQLite under the covers, allowing you amazing ability to store masses of documents on a device for offline use scenarios. Our technology is optimized with capabilities like the ability to only send “diffs” of data changes for optimal performance as well as handling “save conflicts” and resolution, which is important for offline scenarios that allow updates.

​

Can we get the source code?

The core source code in the “engine room”, so to speak? Sorry, no. We did think about it, but when we fix something or add a new enhancement, and you’ve forked the code, it becomes harder to maintain. At this point of time, our full dev team is there to take the pain of development away from your team, so to streamline this we manage the source. 

 

Important point: Buzzy differs from a lot of development platforms in that the custom (non-core) sources are your Figma designs and extensions you’ve applied. This is all created and maintained by you.

​

Additionally, using Figma as a "source" to your application keeps your options open. There are a number of Figma to front-end code solutions out there, so if you decide you’d rather go the "build" approach later, you could use one of those tools to take your Figma designs and turn them into code. Note these solutions still require a bunch of “heavy lifting” code work, as they only give you the front-end; you still have to code the rest of the solution including the database, data binding, business logic and any specific functionality that you need, like offline support or native capabilities like geolocation, tracking and bluetooth (BLE) integration.