Add-on Services
Build’s marketplace (build.io/add-ons) offers managed services, databases, caches, search, email, and AI inference, that you can attach to any app. For a walkthrough of provisioning add-ons from the dashboard, see Databases & Add-ons.
Catalog
Section titled “Catalog”Add-ons fall into two billing groups:
- Build.io add-ons run on Build’s infrastructure and are billed on your Build.io subscription. They draw from your bundled add-on credits before à la carte billing applies.
- Partner add-ons are provisioned through Build but provided and billed separately by the partner. They don’t appear on your Build.io invoice and aren’t covered by enterprise add-on credits.
| Add-on | CLI name | Service | Status |
|---|---|---|---|
| Schema To Go | schema-to-go | PostgreSQL | GA |
| Cache To Go | cache-to-go | Redis | GA |
| Ave To Go | ave-to-go | MariaDB/MySQL | GA |
| Donkey To Go | donkey-to-go | MongoDB | GA |
| Spandex To Go | spandex-to-go | ElasticSearch / OpenSearch | GA |
| Sequel To Go | sequel-to-go | Microsoft SQL Server | GA |
| Infer To Go | infer-to-go | AI model inference | Beta |
| Mailer To Go | mailertogo | Transactional email | GA |
The CLI name is what you pass to addons:create. Each add-on’s page covers its connection details and plans.
Provisioning an add-on
Section titled “Provisioning an add-on”bld addons:create schema-to-go:basic -a my-appThe argument is service:plan. Once provisioned, the add-on’s connection details are set as config vars on your app automatically (for example, DATABASE_URL for schema-to-go), and your dynos restart to pick them up.
Optional flags let you customize the addon at creation time:
bld addons:create cache-to-go:premium-0 -a my-app --name my-cache --config MAXMEMORY_POLICY=allkeys-lruListing and inspecting add-ons
Section titled “Listing and inspecting add-ons”bld addons -a my-app -j | jq '.[] | {name, plan: .plan.name, state}'bld addons:info my-addon-name -jAttaching an add-on to another app
Section titled “Attaching an add-on to another app”Add-ons aren’t limited to the app that provisioned them. Attach an existing add-on to share it across multiple apps (for example, one Postgres instance shared between a customer-facing app and an admin app):
bld addons:attach my-addon-name -a other-appDetach by attachment ID (find it via bld addons:info):
bld addons:detach ATTACHMENT_IDRemoving an add-on
Section titled “Removing an add-on”bld addons:destroy my-addon-name -a my-appThis permanently deletes the underlying resource (database, cache, etc.) along with its data. There’s no confirmation prompt when scripted, so double-check the addon name before running this against a production app.
Plans and pricing
Section titled “Plans and pricing”Each Build.io add-on’s page lists its plans, list prices, and the service:plan provisioning name to pass to addons:create. Mailer To Go’s plans are listed below. Start on the cheapest tier that fits your data. Every service lets you move up or down between plans later.
Mailer To Go
Section titled “Mailer To Go”Transactional email.
| Plan | Provisioning name | Price / mo |
|---|---|---|
| Micro | mailertogo:micro | $9 |
| Mini | mailertogo:mini | $19 |
| Small | mailertogo:small | $79 |
| Startup | mailertogo:startup | $149 |
| Chatty | mailertogo:chatty | $299 |
| Verbose | mailertogo:verbose | $499 |
| Wordy | mailertogo:wordy | $1,500 |
Prices are monthly list prices. The Mailer To Go marketplace page carries the current plan list.
