Take Grok output live on EU infrastructure
Grok now publishes its own apps on grok.me, so the open question is no longer whether a site can go online but where it is served and under which law. VibeDeploy answers with Belgian infrastructure: the code arrives through a GitHub push, an upload or a deploy call Grok makes, and every later revision takes the same route.
Why VibeDeploy for Grok
xAI's August 2026 announcement gives every Grok plan the same publishing kit: a grok.me address per app, your own domain if you want one, and an export to GitHub. What it leaves open is the data-centre location behind those addresses, which is the first thing a European project has to settle. Routing the exported code to VibeDeploy settles it: serving happens in Belgium under EU law, and publishing is a push, an upload or an API call Grok places itself.
A publish path built for chat output
Single-file HTML is served without a build step, and a project that has one compiles from its GitHub repository. Whether you upload it in the dashboard or hand Grok the deploy guide so it calls the HTTP API, the result is identical: files served, URL returned.
Jurisdiction settled before launch
The site runs in EU data centres under EU law, with a DPA on every paid plan. For client work and lead-collecting pages, that is a compliance answer you give once instead of re-litigating it per project.
Revisions stay cheap
Ask Grok for a new version, push it through the same route, and roll back with a snapshot if the previous one was better. Flat plan pricing means iteration never shows up on the invoice.
The Grok to production workflow
- 1
Let Grok build the first version
Describe the site to Grok on the web or in its mobile app. Grok Build, open to every plan since August 2026, assembles a working version inside the conversation, and you refine it there until it is right.
- 2
Open your VibeDeploy trial
Start the 14-day trial at vibedeploy.eu; no card is requested, and a custom domain, automatic SSL and EU hosting are all part of it. The dashboard is in front of you within a minute.
- 3
Push the project to a repository
Grok's Export to GitHub sends the full project to a repository of yours. Select New Site in the dashboard, choose From GitHub and link that repository: anything carrying a package.json is compiled on every push and served at name.vibedeploy.eu, while plain HTML goes in by upload.
- 4
Or make Grok file the deploy
The deploy guide exported from the dashboard, pasted into the Grok conversation, teaches it to submit the files to the API itself. When its environment cannot reach the web, the guide has Grok produce a one-click deploy page that you open in your own browser.
- 5
Or hand over the files directly
Finished files travel without GitHub too: drop one HTML page, a ZIP archive or the whole output folder onto the dashboard and it is served as one site. Anything that still has to be compiled, a package.json without a dist or build folder, is turned away until the build has run.
- 6
Finish with your own domain
Enter the domain in site settings and create the CNAME record shown there. The Let's Encrypt certificate provisions unattended, typically inside a minute.
Grok hosting at a glance
How Grok's default hosting and a generic alternative compare to VibeDeploy.
| Feature | Grok default / generic alt | VibeDeploy |
|---|---|---|
| Public URL for visitors | Yes, a grok.me address (Grok Build) | Yes, instantly |
| Built-in publishing | Publish to grok.me, export to GitHub | Upload, GitHub build or deploy guide |
| Custom domain + SSL | Custom domains supported; plan limits not stated | Included on every plan |
| Hosting location | Not stated in xAI's announcement | EU (Belgium) |
| Rollback snapshots | Not covered in xAI's announcement | Yes, on every plan (3 to 30 days back) |
Common questions about deploying Grok
Do I need a paid Grok subscription?expand_more
No paid tier is required on either side. According to xAI, building in Grok has been part of every plan since August 2026, and the VibeDeploy trial runs 14 days without a card. Prompt to live URL is possible without an upfront payment anywhere in the chain.
Grok wrote the site to /home/workdir/artifacts/index.html. How do I get it out?expand_more
That folder is the working directory of Grok's remote sandbox; nothing was written to your device. Use the download on the file card in the chat, or have Grok output the complete index.html in a code block. The saved file can then be uploaded here and served from Belgium.
Which route takes a Grok project's code out of Grok?expand_more
Through GitHub, which is the export xAI documents: Grok Build sends the complete project into a repository, and VibeDeploy builds from it on every commit. The alternatives are the deploy guide, which lets Grok submit the files to the HTTP API by itself, or files you saved yourself and drop onto the dashboard.
Can I connect Grok to VibeDeploy over MCP?expand_more
Not yet as a tested path. Grok's connector settings let you register your own MCP endpoint, which in principle covers https://mcp.vibedeploy.be/mcp and its OAuth sign-in, but we have not run that combination ourselves. Dependable today: the deploy guide in the conversation, a linked GitHub repository or an upload.
What kinds of Grok builds can VibeDeploy host?expand_more
Static sites and single-page apps, whether Grok produced one HTML file or a project that compiles on push. Should an application need its own continuously running server, it can run beside the site as a container, which an MCP client such as Claude or Cursor deploys with deploy_app. An app wired to Grok's built-in APIs deserves one test run outside Grok before launch.
Where does my site run?expand_more
In a Belgian data centre on VibeDeploy's own infrastructure, keeping visitor data inside the EU. For GDPR obligations and a European audience that is the property that counts, and paid plans include a DPA.
More tool workflows
Put your Grok work into production
14-day free trial, no credit card. Your own domain and snapshots included. Runs on EU infrastructure.