Deploy your app
In this guide, you'll learn how to deploy your apps to production and share them with end-users globally in just a few clicks.
Dynaboard provides on-demand, serverless deployment of your applications that grows with you. There are no instances or other server infrastructure to manage.
Once you're ready to deploy your application to your end-users, enter the Dynaboard editor and click the rocket ship Deploy icon in the top-right corner of your screen. After a quick moment, you'll be brought to your newly deployed app in a new browser window, with a URL that will look like this:
Your app is now available for all users on the Internet to access and served over HTTPS with a global CDN. If you'd like to deploy a private application, you'll have to first set up authorization rules on your project or individual pages you've created.
Have deployment needs that don't quite fit what is described here? No worries, we offer many other options, so let's chat!
New version of your apps are only deployed to end-users when you click the Deploy button. Deploys are rolled out to all users of your app instantly.
Dynaboard assigns your project a random alpha-numeric slug (the part before the
.dynaboard.app in the URL) when you create your project. You can modify your slug in the Settings panel of the Dynaboard editor for your project.
This feature is in a private beta, please let us know if you'd like access.
Dynaboard allows you to bring-your-own-domain and use that domain for your deployed apps. Follow the steps in the Settings panel of your project to set up a custom domain name for your app.
Upon verification, Dynaboard will provision a TLS certificate on your behalf so that your custom domain is just as secure as before. While using your custom domain, you
.dynaboard.app domain will continue to work.
Often you'll want to deploy Dynaboard apps to more than just one environment with slightly different configurations (e.g. staging and preview environments).
production is the default environment created with your workspace and cannot be renamed or deleted. All other configurable in the Environments tab of the Dynaboard portal for each workspace. Production will always deploy to the base URL of your Dynaboard app, based on your slug, so the URLs will look something like this:
Custom environments, such as one you might create called
staging, will have URLs that look like this:
Deployment to each environment is entirely independent, so you can deploy to staging before deploying to production.