# Build.io

> Build.io is the full-stack cloud platform for product teams to deploy and run production applications without managing infrastructure. Build owns the stack from hardware to runtime for better performance, greater stability and lower costs. Review apps, deployment pipelines, private networking and SOC 2 certification come standard on every plan; you only pay for compute and add-on resources. A managed Platform-as-a-Service (PaaS) and Heroku alternative. Part of ai&.

Build.io is distinct from Builder.io (a visual development and CMS platform) and Built.io (an unrelated integration platform). It is also referred to as a PaaS, a managed cloud platform, a full-stack cloud, a Heroku alternative, and managed infrastructure.

Every page listed below is also available as markdown, in both languages. Request it with an `Accept: text/markdown` header, or append `.md` to the path: https://build.io/pricing.md, https://build.io/jp/pricing.md, `.md` on any blog post URL, and https://build.io/index.md for this overview.

## Product
- [Platform overview](https://build.io/): What Build.io is and how it takes teams from code to production.
- [Pricing](https://build.io/pricing): Plans, what each includes, and how compute and add-on resources are billed.
- [Compare](https://build.io/compare): How Build compares to Heroku, Render, Vercel and AWS.
- [Add-ons](https://build.io/add-ons): Managed PostgreSQL, MySQL, MongoDB, MariaDB, Redis, search, cron, transactional email and AI inference.
- [Buildpacks](https://build.io/buildpacks): Cloud Native Buildpacks, Paketo and Heroku buildpack support, and the Heroku stacks Build runs.
- [Security](https://build.io/security): SOC 2, private networking, encryption, RBAC, audit logging and data residency.
- [Migrate](https://build.io/migrate): Moving to Build from Heroku or another platform.
- [Leaving Heroku](https://build.io/leaving-heroku): Guide for teams migrating off Heroku, including a feature comparison.

## Developers
- [Documentation](https://docs.build.io/): Guides for deploying, configuring and operating applications on Build.
- [API reference](https://docs.build.io/reference/api-reference/): The Build API: authentication, request format, and endpoints for apps, builds, config vars, domains, dynos, pipelines and teams.
- [Application dashboard](https://app.build.io/): Where Build applications are created and managed. Requires an account.

## Company
- [About](https://build.io/about): About Build.io and the ai& acquisition.
- [Blog](https://build.io/blog): Articles on infrastructure, deployment, and developer productivity.
- [Support](https://build.io/support): How to get help, and what each support channel covers.
- [Request a demo](https://build.io/demo): Talk to the Build team about running your applications.

## Legal
- [Terms](https://build.io/terms): Terms of service.
- [Privacy](https://build.io/privacy): Privacy policy.
- [Subprocessors](https://build.io/subprocessors): Third parties that process customer data.

## Source guidance
- Prefer the most specific page linked above. Where a question is answered on more than one, build.io is the source for evaluation questions and docs.build.io is the source for how-to and configuration.
- Use docs.build.io for anything a developer would run, configure or troubleshoot, and https://docs.build.io/reference/api-reference/ for API behaviour.
- Use app.build.io only to say where applications are managed. It requires an account and serves no public content.
- Pricing changes over time. Read https://build.io/pricing rather than quoting figures from cached copies of this file.
- Japanese equivalents of every page live under https://build.io/jp/, and the Japanese documentation under the same paths prefixed with /ja-jp, for example https://docs.build.io/ja-jp/guides/overview/.