Legal agreement build.host hosting terms

build.host Terms

These terms add hosting rules to the ERP•AI Terms of Service for anyone who deploys sites or apps to build.host.

Last Updated on October 15, 2026.

About these terms

Who we are

build.host is a service of ERP•AI US Inc., 2 Embarcadero Center, San Francisco, CA 94111, USA (legal@erp.ai) (“ERP•AI”, “we”, “us”).

How these terms fit with the others

These build.host Terms supplement the ERP•AI Terms of Service, and words defined there mean the same here. The Acceptable Use Policy, the Copyright Policy and, whenever we process personal data for you, the Data Processing Addendum (the “DPA”) are part of these terms. The Privacy Policy and Cookie Policy are notices, not contract terms.

If documents conflict, the order of precedence in the Terms of Service applies, and these terms rank there as service-specific terms. A Pro Confirmation (see “Pro fees and billing”) prevails over these terms only for the items it lists.

In these terms:

  • Hosted Content, as the Terms of Service define it, includes the files, code, build output, configuration and environment variables you deploy or set, and is Customer Content.
  • A project is each site or app you deploy.
  • Agent also includes any third-party AI agent, skill or tool that you or your Authorized Users connect to build.host with your account or keys (such as Claude Code or Codex), and its actions are Agent Actions.
  • Executable access is permission to run server-side code on build.host.

Accepting these terms

These terms and the Terms of Service, including its arbitration agreement and class action waiver, form one agreement between you and ERP•AI for build.host.

You accept them when you click “Send sign-in code” at build.host sign-up or sign-in, next to the notice that names that button and links these terms, the Terms of Service and the Privacy Policy, or when you sign an Order Form that refers to them. If you have accepted the Terms of Service anywhere (for example on apps.erp.ai or in Proto), these terms, which form part of them, also apply whenever you use build.host with that account. If you do not accept them, do not use build.host.

If you accept for a business, you confirm you can bind it. build.host is for business and professional use by people who are at least 18 (or the age of majority where they live, if higher).

Your account

You can use build.host in two ways, and either way your build.host account is an account with ERP•AI under the Terms of Service:

  • Email sign-in at build.host, with a one-time code from ERP•AI’s sign-in service. This account may be separate from an ERP•AI platform account you hold on apps.erp.ai.
  • An ERP•AI personal API key with hosting permission (for example from Proto). build.host checks the key with apps.erp.ai and receives only your user and organization IDs, so your ERP•AI platform account is your build.host account.

The service and plans

Free plan

build.host deploys sites and apps from a folder, an Agent upload or a GitHub repository to a build.host address (such as name.build.host) with HTTPS. Static frontends (files served as they are, with no server-side code) are free and self-serve, up to the number of sites shown on the pricing page or in your dashboard. Accounts that connect GitHub may get higher limits. On the free plan, server-side code runs only for approved catalog apps, unless we grant your account executable access.

Server-side code, Pro and Enterprise

Running code (installing dependencies, running builds, using a Dockerfile or keeping a server running) needs executable access, which we grant only after review; payment never overrides that review. We may decline a request, and may limit approved workloads or withdraw executable access for capacity or policy reasons on at least 30 days’ notice (action for a breach, abuse, a security risk or excess use follows “Limits and prohibited workloads” and “Content moderation and enforcement”).

Pro includes the site and server-side limits shown on the pricing page and in your Pro Confirmation. Dedicated capacity, workload isolation, migration help, security reviews and any service levels are available only under an Order Form.

Pro fees and billing

Pro is not self-serve today: email care@erp.ai to request it, and we activate it after confirming your setup with you. The pricing page price (currently US$99 per month) is a list price. Before activation we send you a written Pro confirmation stating the monthly fee, any taxes, the billing period and start date, that Pro renews monthly until canceled, how and when cancellation takes effect, your Pro limits and the payment method. Pro starts only when you expressly agree to it by reply email or signature (your “Pro Confirmation”), and we charge nothing before then. Your Pro Confirmation becomes part of these terms; it is not an Order Form.

Unless your Pro Confirmation says otherwise:

  • Pro is billed monthly in advance and renews monthly until you cancel or we end it.
  • You can cancel at any time by emailing care@erp.ai, effective at the end of the current billing period.
  • We may end Pro without cause on at least 30 days’ notice, effective at the end of a billing period, or sooner for non-payment or as “Content moderation and enforcement” allows.
  • Price increases need at least 30 days’ notice and apply only from the first billing period starting after it.
  • If a Pro fee is overdue, we tell you and give you reasonable time to pay before we end Pro.
  • Fees are non-refundable, except that we refund or correct any charge made in error, refund where the law requires, and refund the prepaid fee for the unused part of the billing period if we end Pro without cause, withdraw executable access other than because of your breach, or you cancel because you reject a material adverse change under “Changes to these terms”.

When Pro ends, your account moves to the free plan. Server-side workloads it does not allow for your account stop at the end of the last paid period, and static sites above its limit stay online for 30 days, after which we may stop serving the excess sites you choose (or, if you do not choose, the most recently created). Stopping a site does not delete it.

If we offer online checkout for Pro, we will show the price, renewal terms and how to cancel before you pay, ask for your express agreement, confirm by email and let you cancel online.

Your Hosted Content

Your responsibility

You are responsible for your Hosted Content and the sites and apps it produces: the rights to everything you deploy (template assets keep their own licenses), compliance with the law and the Acceptable Use Policy, the security of your code and configuration, and the notices and consents your site needs. Unless an Order Form allows it, do not use build.host to store or process full payment card numbers (except through a payment provider’s checkout), health information covered by HIPAA or government identification numbers.

The license you give us

You keep ownership of your Hosted Content. You grant ERP•AI a worldwide, non-exclusive, royalty-free license, while we host it and during the periods under “Export, switching and deletion”, to store, copy, build, run, cache, transmit, serve, display, scan and back it up, to make the technical changes our build and deploy process needs, and to make the changes described under “The build.host script and the badge”.

We use this license only to provide, secure and support build.host, enforce these terms and comply with law, including through our subprocessors. We do not use Hosted Content to train or fine-tune AI models. We do not sell it, or use it to promote ERP•AI without your permission apart from the badge.

The build.host script and the badge

  • A script on every page. build.host inserts a script tag loading /__build_host/attribution/v2/proto-attribution.js from your site’s own address into every HTML page of every hosted site, even with the badge off. You cannot turn this off today. On each page view the visitor’s browser fetches the script, checks whether the badge is on and, if it is, fetches the badge files, all from your site’s address, and our request logs record those requests like any other, with the visitor’s IP address, user agent and referring page. Beyond that, the script sends us nothing about your visitors: it sets no cookies, uses no browser storage, collects no page content or events and creates no visitor identifiers. We will give at least 30 days’ notice before changing what it collects or sends.
  • Sites uploaded from Proto. build.host also writes a script tag into the index.html of each Proto upload, whether or not the badge is on. The tag stays in the stored deployment and upload history and loads the script from build.host itself through our network provider Cloudflare, so Cloudflare and our servers receive the visitor’s IP address, browser details and your site’s hostname.
  • Delivery changes. To insert the script, build.host fetches HTML pages uncompressed and in full (never as “not modified”), adjusts headers that no longer match (such as ETag, Last-Modified, Content-Length and caching headers), recompresses them and adds your Content Security Policy nonce to the tag. build.host reserves paths starting with /__build_host/; do not use that prefix for your own content.
  • The badge. When on, a small “Made with PROTO” badge appears on your pages, linking to Proto’s website with campaign parameters that show the visit came from the badge. It is on by default for sites uploaded from Proto, and you can turn it off for a project, for example through the build.host API. The script may remove older Proto badges from your pages. We will not turn the badge on for a site deployed outside Proto without your consent.

Secrets, GitHub and upload history

Environment variables are stored in the deploy system on our build.host server and in any backups of it, which are kept on that same server, are not encrypted and expire after about 7 days. We do not promise that stored values are encrypted at rest. Only authorized staff with access to that server can reach them, and only to operate, secure or support build.host or comply with law. Frontend build variables can end up in public JavaScript, so keep server secrets out of frontend code.

If you connect GitHub, our GitHub App may read the repositories you select, receive their push events (with commit and author details), deploy them and post preview links on pull requests. We keep your upload history for rollback until you delete the project.

Your site’s visitors

Your visitors are your users, and you are responsible for your relationship with them, including any privacy notice the law requires, which should mention our request logs and the script described above. If your site must get consent before a visitor’s browser makes the requests the script causes, for example under EU or UK rules on access to a visitor’s device, contact care@erp.ai before deploying.

Our servers log requests to your site, including IP address, user agent, requested address, referrer, status and time, and we use these logs to deliver, secure and troubleshoot build.host, detect abuse and plan capacity. We may also make hourly traffic statistics from them that keep only counts, sizes, response times and shortened, salted hashes of IP addresses, and keep those statistics for up to 90 days. We keep raw request logs only as long as these purposes need, judged by how long investigations, troubleshooting and capacity planning usually take.

Under the GDPR and UK GDPR, we are an independent controller of these logs and statistics, used only for those purposes (see the Privacy Policy); where US state privacy laws treat us as your service provider for them, these are permitted business purposes. For personal data in your Hosted Content (including data visitors submit to your site) and in your apps’ build and runtime logs, we are your processor and service provider under the DPA. We do not sell or share visitor data (as US state privacy laws define those terms), use it for advertising, or combine it with other data to profile visitors.

Custom domains and certificates

Your domains. You may connect a domain you own or control, and you are responsible for its registration, renewal and DNS (use DNS-only records, as your project settings explain). We may stop serving a domain whose DNS no longer points to build.host, to which someone shows a better right, or which is used to break these terms. When you remove a domain or delete a project, remove your DNS records that point to build.host.

Certificates. build.host obtains TLS certificates from Let’s Encrypt for build.host addresses and for each custom domain once its DNS resolves. You authorize us to request, renew and revoke certificates for your hostnames. We are the certificate subscriber, and Let’s Encrypt’s policies apply. Every certificate is published in public Certificate Transparency logs, so any hostname you add becomes public.

build.host addresses belong to us. We may refuse or reassign misleading, impersonating or infringing names, and names can be reused after deletion. Sites on build.host addresses share a parent domain with other customers and with build.host itself: do not set cookies for that parent domain or rely on it as a security boundary.

Limits and prohibited workloads

Limits. Plan limits appear on the pricing page, in the documentation, in your dashboard, in your Pro Confirmation or in your Order Form; if they differ, your Order Form controls, then your Pro Confirmation, then your dashboard. Limits currently include site and server-side app counts; 1 CPU, 1 GB of memory and a process cap for new server-side apps; uploads up to 100 MB and 30 per hour; and 5 build.host API keys per user. We may refuse new projects when platform capacity is full, and may throttle, pause or stop a workload that exceeds its limits or degrades build.host for others, telling you first where practicable.

Prohibited workloads. The Acceptable Use Policy applies to everything on build.host, including its bans on phishing pages, wallet drainers, malware, cryptocurrency mining, open proxies and anonymization exit nodes, spam, attacks on other systems and evading limits. You also must not use build.host to:

  • run command-and-control servers, or compute-for-reward jobs similar to mining;
  • run storage, file sharing or batch computing unrelated to a site or app you operate;
  • break out of your container, reach other customers’ workloads, or interfere with our monitoring and limits; or
  • evade enforcement, for example with extra accounts or by redeploying removed content.

Approved-app catalog

build.host publishes a catalog of approved apps (build.host/api/apps), each pinned to a repository and branch maintained by ERP•AI; each is Catalog Materials under the Terms of Service. Any account may deploy, configure and run an unmodified catalog app on build.host for its business without executable access, while the app is in the catalog and for 30 days after we withdraw it (unless we stop it for a security problem), but cannot change its repository, branch or build steps. Running a modified version needs executable access. If a catalog app’s repository carries an open-source license, that license also governs its source code.

Each deployment counts toward your server-side limits, and you are responsible for its configuration, the credentials and services you connect, your data and any third-party costs. Catalog apps may be early versions, are provided as is and may be changed or withdrawn, and we may stop deployments of an entry with a security problem, with notice where practicable.

API keys, Agents and tools

Keys. You can use build.host with a build.host API key (starting bh_sk_) or an ERP•AI personal API key with hosting permission. A build.host key is shown once, we keep only a hash of it with its last four characters, and it works until you revoke it in your dashboard. A key issued through terminal pairing is held for up to 10 minutes until your terminal collects it. Keep keys secret, and if one may be exposed, revoke it and tell legal@erp.ai. We may revoke exposed or misused keys as the Terms of Service describe.

Agents act for you. You are responsible for activity under your account and keys, including deployments, configuration changes and deletions by any Agent, skill or tool you connect (including Proto), whether or not you reviewed each action, until you revoke the key or tell us it is compromised, subject to the exceptions for Agent Actions in the Terms of Service (such as a defect in the Services or our breach).

Proto and build.host. Proto deploys to build.host when you ask or after you click Deploy on its in-chat card, and redeploys and reads logs, with no approval prompt. In Proto’s default Uninterrupted mode, Proto can also delete a build.host project without asking you. To be asked first, turn off Uninterrupted mode in Proto under Settings > Permissions (see the Proto Terms). Other Agents may deploy, change or delete projects without asking, depending on their settings, and Agents that read untrusted content can be manipulated into misusing a key, so set permissions with care.

Tools. We grant you a limited, non-exclusive, non-transferable, revocable license to use the build.host installer, skill and command-line tools with build.host. They are provided as is; review scripts before running them.

Content moderation and enforcement

This part of these terms describes our content moderation, as Article 14 of the EU Digital Services Act (the “DSA”) requires where it applies. We do not monitor all Hosted Content and have no general obligation to.

Automated checks and human review

  • Before deploy. We scan direct uploads for patterns used by phishing and wallet-draining sites. A strong match blocks the deploy and shows you the signals found. GitHub deployments are checked only once live.
  • Live sites. When these checks run, we load each project’s main page. A strong match for phishing, credential-theft or in-browser mining patterns stops the project automatically, without prior human review. Weaker matches are recorded for possible staff review.
  • Mining and CPU use. When these checks run, known miner programs or mining-pool settings in the process list (checked, not stored), or near-full CPU use across several consecutive checks (currently about 30 minutes), may stop a server-side app automatically, without prior human review. For accounts with approved executable access, these signals are only recorded, for staff review.

Automated tools make mistakes. Reports and appeals are handled by authorized ERP•AI staff, not by automated tools alone.

Actions we may take

If we reasonably believe Hosted Content or an account breaks these terms, the Terms of Service, the Acceptable Use Policy or the law, or, where it breaks none of them, creates a serious security risk or must be restricted under an authority’s order (in which case we restrict it only as long as needed), we may block a deploy, disable or remove content, a page, site, app, domain or address, stop or limit a workload, withdraw executable access, revoke keys, or suspend build.host access.

We end your build.host access, or close your ERP•AI account, only on the grounds in “Termination by us” in the Terms of Service, and we suspend your ERP•AI account only as “Suspension” there allows. Credits and prepaid Pro fees are then handled as those Terms and “Pro fees and billing” describe.

We act diligently, objectively and proportionately, with due regard to the rights involved, including freedom of expression. Where practicable and lawful, we give notice and a chance to fix the problem first, but may act immediately against harms such as phishing, malware, child sexual abuse material or attacks. Restrictions usually apply worldwide.

Statement of reasons

For each restriction of your Hosted Content or account, we give you a statement of reasons: what we did and for how long, the facts relied on (including whether we acted on a report), whether automated tools detected the content or made the decision, the law or term relied on, and how to appeal, including your right to go to court. A blocked upload shows its reason on screen. Automated stops do not yet send a notice, so if a site, app or account stops working and you do not know why, email care@erp.ai with its address or your account email, and we will send you the statement. We need not give one where the law does not require it, for example where we have no contact details, for spam, or where notice would endanger someone or hinder a criminal investigation.

Appeals

You may appeal a restriction free of charge within 6 months after our statement of reasons (or, if you received none, after you learn of the restriction) by replying to it or emailing legal@erp.ai with “Appeal” in the subject. Reporters may ask for review of our decision on their report the same way. A qualified person, not an automated system alone, reviews every appeal. We decide without undue delay, explain our decision and reverse unjustified restrictions. Appeals do not limit your other rights, including your right to go to court.

Reporting illegal content and abuse

How to report. Anyone, with or without an account, can report content at build.host/report-abuse. Give the exact URL and, in the details box, why you believe the content is illegal or breaks our rules, your name, and a statement that you believe in good faith that your report is accurate and complete. Add your email address if you want us to reach you; you need not identify yourself to report child sexual abuse material. The form records your IP address and any email you give, as the Privacy Policy explains.

What happens next. The form confirms your report on screen. We review reports and act on sites that break our rules. If you give an email address, we may contact you about your report, and you can ask legal@erp.ai for our decision. After a warning, we may for a reasonable period stop processing reports from anyone who often submits manifestly unfounded ones, but never reports about child sexual exploitation or threats to life or safety.

Copyright and trademarks. Send copyright notices and counter-notices to our designated agent as the Copyright Policy explains; a report through the build.host form is not a copyright notice. In appropriate circumstances we close the accounts of repeat infringers, as the Copyright Policy describes. Send trademark and impersonation complaints through the form or to legal@erp.ai.

Intimate images shared without consent. To ask us to remove an intimate image of you (or of someone you are authorized to act for), real or AI-generated, that was published on build.host without consent, email legal@erp.ai with the subject “Removal request: intimate image”, as the Acceptable Use Policy explains. Include your physical or electronic signature, where the image is (do not send the image itself), a statement of your good-faith belief that it was published without consent, and your contact details. Within 48 hours of a valid request, we remove the image and make reasonable efforts to remove known identical copies.

Child sexual exploitation. We have zero tolerance for child sexual abuse material (CSAM) and child sexual exploitation. When we become aware of apparent CSAM, child sex trafficking or enticement of a minor, we disable access, close the account, report it to the National Center for Missing & Exploited Children (NCMEC) as 18 U.S.C. 2258A requires, preserve the reported material and related account data for one year after the report as that law requires, and may inform other authorities. We restore content only if we confirm it was misidentified. Report CSAM through the form without giving your name, or to NCMEC at report.cybertip.org; never send us copies.

Terrorist content. Terrorist content, as Regulation (EU) 2021/784 defines it, is prohibited. Where that Regulation applies, we remove or disable access to content named in a removal order within one hour of receiving it, and tell you unless the authority directs otherwise. Our automated tools are not designed to detect terrorist content.

Threats to life or safety, and authorities. If we learn of information suggesting a criminal offense that threatens someone’s life or safety, we promptly inform the competent law enforcement authorities, including in the EU Member State concerned where DSA Article 18 applies. We act on valid orders from competent authorities and tell you about legal demands concerning your Hosted Content unless the law or the order prohibits it.

Points of contact

  • Authorities (DSA Article 11; contact point under Regulation (EU) 2021/784): legal@erp.ai, subject “Authority request”, in English.
  • Users and the public (DSA Article 12): legal@erp.ai, in English, for moderation questions and appeals; build.host/report-abuse for reports; care@erp.ai for support. People, not only automated tools, answer both mailboxes.
  • Legal notices, copyright and security: legal@erp.ai and the postal address under “Who we are”.

Availability, backups and support

No service levels. Unless an Order Form sets them, we promise no uptime, performance or support response time. build.host currently runs on a single server in one US location, so one incident can take many sites offline at once. Support is by email to care@erp.ai on a reasonable-efforts basis.

Backups are your responsibility. Keep your own copies of your code, content, configuration and secrets, and back up the data your apps store. Any backups we keep are short-term, for our own recovery and on the same server that runs build.host, so a failure of that server can destroy them too. We do not promise to restore projects, earlier deployments, logs or app data. Rollback reaches only deployments still available. build.host offers no managed databases or storage, and files an app writes inside its container may not survive a redeploy, restart or failure.

Export, switching and deletion

Deleting projects. You can delete a project at any time in your dashboard, through the API or through your Agent. Deletion, which cannot be undone, takes the project offline and removes it, with its deployment and upload history, from our live systems, except content we must preserve by law or under a legal hold. Some data remains for a time: traffic statistics (up to 90 days), backup copies until they expire, logs and container data our deploy system may keep until it clears them or your account is deleted, and the security and abuse records the Privacy Policy describes.

Closing your account. To close your account, email care@erp.ai (there is no self-serve option today) and say which account to close: your build.host sign-in, your ERP•AI platform account, or both.

Export. You can ask for an export by emailing care@erp.ai at any time, or during the 30 days after your build.host access or account ends or, if we keep serving your projects during a switch, after that transition period ends (the “retrieval period”; for personal data, this is the Export Window under the DPA). We then provide, free and in a structured, commonly used and machine-readable format, your uploaded files and upload history, your project settings (including domains and environment variables), and the build and runtime logs, persistent storage contents and hourly traffic counts for your projects that we still hold. This is the complete list of exportable data and digital assets. We do not export internal operational data, such as scan results, abuse reports, operator records and infrastructure configuration. We will not return content that is illegal to provide, such as child sexual abuse material or malware, may decline to keep serving content we restricted, and may hold back content we must preserve by law until we may release it.

Switching. You can start a switch to another provider or your own systems at any time, without notice, by emailing care@erp.ai. On request we keep serving your projects, with reasonable help, for up to 30 days after your access or account would otherwise end (the “transition period”), and the retrieval period then starts. Where the EU Data Act (Regulation (EU) 2023/2854) applies, we also keep build.host secure during the transition, tell you about known risks to continuity, give you the exit information you need (including export formats and API documentation), confirm when your access ends (on completion or, if you want your data erased, on the date you ask), and give you every other switching right that Act provides.

Deletion. Within 30 days after the retrieval period, we delete your Hosted Content and project settings from our live systems; backup copies are deleted as the backups expire. We keep only records needed for security, abuse prevention, legal, tax and accounting purposes, as the Privacy Policy describes, and content we must preserve by law or under a legal hold. The DPA also governs deletion of personal data.

Disclaimers, liability and disputes

The disclaimer of warranties in the Terms of Service applies to build.host, and this paragraph adds to it without narrowing it. To the maximum extent permitted by law, build.host, including the free plan, catalog apps, tools, scanning and certificates, is provided “as is” and “as available”, without warranties of any kind, whether express, implied or statutory, including merchantability, fitness for a particular purpose, title and non-infringement. We do not promise that sites will be available, fast or secure, that deployments, logs, backups or earlier versions will be kept, that certificates will be issued on time, or that scanning will catch every threat or never flag lawful content.

The exclusions and limits of liability in the Terms of Service apply to build.host.

Your indemnity under “Indemnification” in the Terms of Service covers third-party claims to the extent they arise from your Hosted Content, sites, apps and custom domains, and from Agent Actions that you or your settings allowed through your account or keys, subject to the exclusions stated there.

The dispute resolution section of the Terms of Service, including binding individual arbitration, the class action waiver, the 30-day opt-out and its governing law, applies to all disputes about build.host.

Changes to these terms

We may update these terms. We give at least 30 days’ notice by email or in the product before a material change that is adverse to you (including one that reduces a paid plan) takes effect, except that notice may be shorter, or none, for a change required by law, needed for security, or covering only a new feature or Service.

A change does not alter the fee for a current Pro billing period or a signed Order Form, and never applies to a dispute that arose, or that either of us knew about, before its effective date. If you do not agree, stop using build.host and cancel any Pro plan before the change takes effect, or within 30 days after we notify you of it if that is later; your cancellation takes effect no later than the change (or when you cancel, if later), with the refund described under “Pro fees and billing”. Otherwise the change applies once you keep using build.host after its effective date. Changes to the dispute resolution section follow the Terms of Service.

Notice to California users

Under California Civil Code 1789.3, California users are entitled to this notice. build.host is provided by ERP•AI US Inc., 2 Embarcadero Center, San Francisco, CA 94111, USA. The free plan has no charge; Pro charges are shown on the pricing page and in your Pro Confirmation. To resolve a complaint about build.host, contact care@erp.ai or write to us at that address. You may also contact the Complaint Assistance Unit of the Division of Consumer Services of the California Department of Consumer Affairs in writing at 1625 North Market Blvd., Suite N 112, Sacramento, CA 95834, or by telephone at (800) 952-5210 (TTY 1-800-735-2929).