thelastapi
Get started free

Host a landing page that ChatGPT or Claude wrote

Host a website generated by ChatGPT or Claude using the thelastapi connector or CLI, with free vibiz.app subdomains, rollback, and custom domains.

On this page 7 sections

You can host a website made by ChatGPT or Claude by connecting the thelastapi remote MCP connector directly to the chat, or by saving the code locally and running vibiz deploy. Both methods give you an active site at https://<slug>.vibiz.app with HTTPS turned on automatically. Deployments keep every version so you can inspect diffs and roll back broken code instantly, and hosting is not charged today while pricing is undecided.

Whether you generated raw HTML files in a browser chat or had an agent generate a full project, you do not need complex pipeline configurations or separate infrastructure accounts to get your site online.

How to publish directly from Claude or ChatGPT

If you created your landing page inside Claude.ai or ChatGPT, you do not have to copy files to your computer or install any software. You can connect your chat interface directly to thelastapi via its Model Context Protocol (MCP) server. See deploy a website from Claude or ChatGPT with nothing installed for a focused walkthrough.

1. Add the custom connector

Use the remote connector endpoint:

Text
https://thelastapi.dev/mcp
  • In Claude (web, desktop, or mobile): Go to Settings ▸ Connectors ▸ Add custom connector. Enter the name Vibiz, paste https://thelastapi.dev/mcp, and click Add. Click Connect, sign in to your thelastapi account, and click Authorize.
  • In ChatGPT: Turn on Developer mode under Settings ▸ Apps ▸ Advanced settings. Create an app using https://thelastapi.dev/mcp and OAuth sign-in, then authorize the connection.

2. Ask the model to deploy

Once connected, ask the assistant to generate and host your site in one instruction:

Text
Use thelastapi to build and publish a landing page for Acme Bakery, with a hero section, pricing table, and contact form.

Under the hood, the assistant calls vibiz_create_project { name: "Acme Bakery" } to set up the project. It then calls vibiz_deploy with the generated files:

JSON
{
  "project_id": "prj_123",
  "files": [
    {
      "path": "index.html",
      "content": "<!doctype html><html><head><title>Acme Bakery</title></head><body><h1>Fresh bread daily</h1></body></html>"
    }
  ]
}

The site goes live at https://<slug>.vibiz.app. One chat call can send up to 300 files, up to 3 MiB per file and 4 MiB in total across the call. Text files are encoded as utf8 and images as base64.

If you need to update copy or styling later, ask the chat model to make the change. The assistant reads the current files using vibiz_code { action: "read" }, updates what changed, and calls vibiz_deploy with only the edited paths.

How to deploy website files from your terminal

If ChatGPT gave you an index.html file, a CSS file, or an entire project directory that you saved to your computer, you can publish it in seconds using the CLI. For a complete guide to starting out, see the Quickstart.

1. Install and log in

Install the @vibiz/cli package globally using npm:

Terminal
npm install -g @vibiz/cli
vibiz login

The vibiz login command prints an authorization URL in your terminal. Open the link in your browser and click Authorize to generate an API key on your machine.

2. Initialize and deploy

Navigate to the directory containing your website files:

Terminal
cd acme-bakery
vibiz init "Acme Bakery"
vibiz deploy

vibiz init provisions default resources (hosting, database, sign-in, and analytics) and writes a vibiz.json file to store your project id. vibiz deploy inspects your folder, hashes your files, uploads any missing assets, and deploys the production build to your live <slug>.vibiz.app address.

When you deploy from a folder, the CLI automatically ignores directories and sensitive credentials. The following paths are never uploaded:

  • node_modules, .git, .next, dist, and .turbo
  • vibiz.json and .env* configuration files
  • Key and secret files (*.pem, id_rsa, .npmrc)

The CLI limits each deployment to 10,000 files and 50 MB per file, with a daily cap of 30 builds per project per UTC day.

How to preview changes and roll back mistakes

When AI models update your code, they can introduce formatting bugs or broken layouts. thelastapi provides version history on every deploy without requiring git setup, as detailed in version history for your website: see what changed and roll back.

Deploying a preview

You can test changes on an isolated URL before pushing them live:

Terminal
vibiz deploy ./site --preview

A preview deployment builds at a distinct preview URL. When you confirm the preview looks right, promote it directly to production:

Terminal
vibiz promote dep_123

A production deployment switches instantly because its build assets and file manifests are already stored.

Checking diffs and rolling back

To see what changed between deployments:

Terminal
vibiz versions
vibiz diff

vibiz versions lists recent deployments with their messages, timestamps, and authors. vibiz diff prints a unified diff comparing your live site to the previous working deployment.

If an update breaks your landing page, revert it immediately:

Terminal
vibiz rollback

You can also roll back to any historical deployment id:

Terminal
vibiz rollback dep_abc123

Restoring an older production version switches traffic instantly. Keep in mind that rollbacks affect your application code and static assets, but do not roll back database rows or schema migrations.

Hosting limits and resource pricing

Hosting is currently free while in development. Here is how hosting resource limits and pricing compare:

Featurethelastapi Limit / PriceDetails
Live hosting price$0Build and site usage recorded at $0 today
Daily builds30 per UTC dayReturns 429 rate_limited once reached
CLI file limits10,000 filesUp to 50 MB per file
Chat MCP file limits300 files per call3 MiB per file; 4 MiB total payload
Built-in addressIncludedFree https://<slug>.vibiz.app with HTTPS
Project restoration7 daysDeleted project data is recoverable for 7 days

If you are running a lean business or personal experiment, read the cheapest way to host a website and database for a side project for an overview of keeping side-project infrastructure costs low.

Adding your own custom domain

Your site is immediately accessible at its <slug>.vibiz.app address, but you can attach a custom domain at any time. Read the full Domains reference for configuration rules.

Connecting a domain you own

To use a domain purchased through another registrar, run:

Terminal
vibiz domains add shop.example.com

The CLI prints the exact DNS records you must create at your DNS provider:

Domain TypeRecord TypeNameValue
Subdomain (shop.example.com)CNAMEshopcname.vibiz.app
Root apex (example.com)A@The IP shown by records_to_set
Apex redirect (www.example.com)CNAMEwwwcname.vibiz.app

When you connect an apex domain like example.com, www.example.com is configured automatically to redirect to your root address. After setting the records, verify them:

Terminal
vibiz domains verify shop.example.com

HTTPS certificates are provisioned automatically as soon as DNS verifies.

Buying a domain directly

You can also search and purchase a custom domain directly from your credit balance:

Terminal
vibiz domains search acmebakery
vibiz domains buy acmebakery.app

Domains purchased through thelastapi require no manual DNS setup. The platform manages the DNS zone, configures HTTPS automatically, and makes the domain available to any of your projects with vibiz domains use acmebakery.app --project prj_123.

Pulling code locally and exporting your project

Code deployed directly through ChatGPT or Claude does not lock you into the browser. You can pull live files to your local machine at any time:

Terminal
vibiz pull my-site

vibiz pull downloads the live deployment files into a folder named my-site. You can open the files in your editor, edit them, and run vibiz deploy whenever you want. You can also view files directly from the terminal without downloading everything:

Terminal
vibiz code ls
vibiz code cat index.html

When you need a complete offline archive or want to migrate to your own infrastructure, run the export command as documented in Export:

Terminal
vibiz export --code -o acme-site.zip

This packages the exact source code of the live deployment, along with a VIBIZ-EXPORT.md architecture guide and .env.example. If your project includes an active database, running vibiz export without flags exports the code, the database as a compressed SQL snapshot, and optional table CSVs.

To begin hosting your ChatGPT or Claude projects, check the Hosting guide, or follow the instructions at Quickstart to connect your workspace.

Frequently asked questions

Can I host dynamic backend code or just static HTML?

You can deploy static HTML pages as well as full application frameworks like Next.js using `vibiz init --template nextjs-saas` and `vibiz deploy`. The hosting platform builds the app, serves it at your `<slug>.vibiz.app` URL, and can be paired with managed database and sign-in resources.

How much does hosting cost on thelastapi?

Hosting is not charged today: builds and live websites are recorded in your usage dashboard at $0 while long-term hosting pricing remains undecided. Each project receives a limit of 30 builds per UTC day.

What happens if an AI agent deploys broken code to my site?

You can revert your live website immediately by running `vibiz rollback` in your CLI or calling `vibiz_rollback` from your chat agent. A production rollback switches your traffic back to the previous working deployment instantly without needing to rebuild.

How do I pull the website files back down to my computer?

Run `vibiz pull <folder>` to write all the files from the live deployment directly into a local directory on your machine. From there, you can inspect the code, edit it in your local editor, and redeploy using `vibiz deploy`.