How to deploy a website from Antigravity in seven steps

To deploy a website from Antigravity, push your task to a GitHub repository and link it to a hosting supplier that builds and serves your site.

Google Antigravity is an agentic improvement level wherever AI coding agents tin plan, write, and trial full projects successful 1 place. However, it doesn’t big websites. Your task stays connected your machine until you people it to a hosting supplier that makes it disposable done a nationalist URL.

Follow these 7 steps to return your Antigravity task from your section machine to a unrecorded website:

1. Review and cleanable up the generated task files.
2. Determine whether the build output is fixed aliases dynamic.
3. Run the accumulation build locally and verify that it works.
4. Push the task to a GitHub repository.
5. Connect the repository to a hosting supplier and configure the build.
6. Point a civilization domain to your tract and alteration HTTPS.
7. Set up automatic redeployment truthful each early push updates the unrecorded site.

If you’re a Hostinger customer, you tin usage Hostinger Connector to deploy straight from the IDE to your hosting scheme pinch a azygous prompt. Similarly, Google Cloud users tin deploy done the Cloud Run MCP server, which connects Antigravity to Cloud Run.

1. Prepare your Antigravity task for deployment

Similar to deploying a website from different integrated improvement environments (IDEs), you request to make judge your Antigravity task is cleanable and free of issues earlier deployment.

Antigravity agents often time off down impermanent files, debug logs, and hardcoded trial values that tin origin problems successful production.

To hole your task for deployment, unfastened it successful Antigravity IDE (not the standalone Antigravity 2.0 desktop app). Then, travel these steps:

1. Open your task files if you haven’t already.
2. Make judge your task has the correct introduction point. For example:
   • index.html for a fixed website.
   • package.json (which defines your commencement script) for JavaScript frameworks for illustration React aliases Next.js.
   • app.py for Python frameworks for illustration Flask.
3. Review your task files and region thing the supplier created for testing that doesn’t beryllium successful production, specified arsenic test-data.json, debug.log, aliases impermanent folders for illustration tmp/.
4. Search your task for hardcoded localhost URLs. Press Ctrl+Shift+F connected Windows aliases Linux, aliases Cmd+Shift+F connected macOS, past look for URLs specified arsenic http://localhost:3000/api/users. Make a statement of the affected files truthful you tin switch these URLs pinch your accumulation URL aft deployment.
5. Run the task locally to corroborate everything still useful aft cleanup:
   • For JavaScript projects, tally npm tally dev aliases npm start, past unfastened the URL shown successful the terminal.
   • For Python projects, tally python app.py, past unfastened the section URL printed successful the terminal.
   • For a plain HTML website, unfastened index.html successful your browser by double-clicking the file.

2. Identify whether your tract is fixed aliases dynamic

Before choosing a host, find whether your task is simply a fixed tract aliases a move app. The introduction constituent you identified antecedently tin springiness a useful clue, but the main mobility is simple: does your task request a server moving successful the background?

A static site consists of HTML, CSS, and JavaScript files that a big tin service directly. A dynamic app needs an progressive server process, specified arsenic Node.js aliases Python, to grip requests, process data, link to a database, aliases make content.

Use the array beneath to place your task type:

What you spot successful your project	Type
Plain HTML, CSS, and JavaScript files pinch nary package.json	Static
A package.json record that uses Vite, React, aliases Vue without server-side rendering	Static
An Astro task pinch the default fixed output	Static
A Next.js task pinch server-side rendering aliases API routes	Dynamic
A Flask, Express, aliases FastAPI backend	Dynamic
A Dockerfile successful the task root	Usually dynamic

You tin deploy fixed sites to astir web hosts, including free platforms specified arsenic Cloudflare Pages and Netlify. Dynamic apps, however, request a big that supports the project’s server runtime. This limits your hosting options and whitethorn summation the cost.

If you built the task wholly done Antigravity prompts and aren’t judge which setup the supplier chose, inquire it: “Is this task static, aliases does it request a server to run?” The supplier tin reappraisal the files it generated and explicate which hosting situation your task requires.

3. Run and verify the accumulation build

Build the accumulation type of your task to make the files your hosting supplier will serve. Most web hosts don’t usage your improvement setup directly. Instead, they service the optimized files created by your project’s build command.

You tin skip this measurement if your task is simply a plain HTML website pinch nary model aliases build tools. Its files are already fresh for deployment.

For framework-based projects, specified arsenic React, Vue, Next.js, aliases Astro, the build bid compiles and optimizes your root files for production. Follow these steps:

1. Install your project’s limitations by moving npm install successful the terminal. If you antecedently ran npm tally dev, they’re astir apt already installed, but moving the bid again is safe.
2. Run npm tally build aliases yarn build, depending connected your project’s setup. This bid processes your root files and creates a production-ready build.
3. Find the output files created by the build command. Common files names see dist/, build/, and out/. Next.js projects usually create a .next/ folder. Check the last lines of the build log if you’re not judge which files your task uses.
4. Test the accumulation build locally. For a fixed output folder, tally npx service dist, replacing dist pinch your existent output files name. This starts a section server that serves the built files. Open the URL shown successful the terminal, past cheque that each page loads, images appear, links work, and navigation behaves arsenic expected. And for a move Next.js build, tally npm tally commencement instead, which launches the Node server needed to service the app.

4. Push your task to a Git repository

Upload your task to GitHub truthful your hosting supplier tin entree and deploy it later. The fastest action is to fto the Antigravity supplier grip the setup.

Open the chat and type this prompt:

Initialize Git, create a .gitignore record for this stack, perpetrate each task files, and push them to a caller GitHub repository named my-new-website nether my account.

The supplier will initialize a Git repository successful your task folder, create a .gitignore file, perpetrate your task files, and push them to GitHub. The .gitignore record should exclude files your big doesn’t need, specified arsenic node_modules/ and .env.

If this is your first clip connecting Antigravity to GitHub, the supplier will instruct you to motion successful and authorize access.

After the supplier confirms that the push succeeded, unfastened GitHub successful your browser and verify that the repository contains your task files.

If you’d alternatively push your task files to GitHub manually, travel these steps:

1. Create a record called .gitignore successful your project’s guidelines files and paste the pursuing content. This tells Git to skip your downloaded limitations (node_modules/), concealed keys and passwords (.env), and build output folders. If your task uses a different output files name, adhd it to the list.

node_modules/ .env dist/ build/ out/ .next/ __pycache__/ *.pyc

2. Go to github.com, motion in, and create a caller quiet repository. Don’t adhd a README aliases .gitignore record connected GitHub – doing truthful creates a perpetrate that will conflict pinch your section repository’s history erstwhile you push.
3. Open the terminal successful Antigravity IDE by selecting View → Terminal and tally the pursuing commands 1 astatine a time:

git init git adhd . git perpetrate -m "Initial commit" git distant adhd root https://github.com/your-username/your-repo.git git branch -M main git push -u root main

Replace your-username pinch your GitHub username and your-repo pinch the repository sanction you created.

After the push finishes, unfastened the repository connected GitHub and corroborate that your task files appear.

5. Choose a hosting supplier and link your repository

Connect your GitHub repository to your web hosting supplier truthful it tin propulsion your code, tally the build process, and people your site. Here are respective celebrated options for hosting your website:

Host	Best for	Free tier
Cloudflare Pages	Static sites that request accelerated world delivery	Yes, pinch unlimited bandwidth
Netlify	Static sites and frontend projects	Yes
Vercel	Next.js and React apps that usage server-side rendering	Yes, connected the Hobby plan
GitHub Pages	Simple fixed portfolios and archiving sites	Yes, pinch a nationalist repository
Hostinger	Static aliases move apps erstwhile you want hosting and a domain successful 1 place	No, starts astatine $3.79/month, pinch a free domain and SSL

Static sites activity good connected free services specified arsenic Cloudflare Pages, Netlify, and GitHub Pages. For a Next.js app that uses server-side rendering, see Vercel aliases different supplier that supports the Node.js runtime.

Hostinger is simply a suitable action if you want to negociate your website, domain, and email from 1 dashboard, whether you’re hosting a fixed tract aliases a move app.

After choosing a host, link your GitHub repository. The process is akin crossed astir platforms:

1. Sign successful to your hosting account.
2. Find the Git aliases GitHub integration.
3. Authorize entree to your GitHub account.
4. Select the repository you created earlier.
5. Deploy your site.

On a Hostinger Business Antigravity hosting plan aliases higher, the steps dangle connected your task type:

• For Node.js apps, including React, Express, and Next.js projects, spell to hPanel → Websites → Add website → Deploy Web App. Choose your domain aliases usage a impermanent one, past click Connect pinch GitHub, prime your repository, and travel the on-screen instructions.

• For fixed sites, PHP projects, and WordPress websites, spell to hPanel → Websites, find your website, and prime Dashboard → Advanced → Git. Click Continue pinch GitHub, authorize the integration, prime your repository, and click Deploy.

Some web app hosting providers inquire you to participate the build bid and output files manually. Use npm tally build arsenic the build command, past participate the output files you identified earlier, specified arsenic dist/ aliases build/.

Hostinger tin observe your model and build settings automatically. Review the detected build bid and output files earlier deploying, and set them if needed.

If your task uses situation variables, specified arsenic API keys aliases database URLs stored extracurricular the root code, adhd them done your hosting provider’s settings earlier deployment.

After configuring the build command, output directory, and situation variables, deploy your tract to your hosting provider.

Once the deployment finishes, your big should show a occurrence position and a URL for your unrecorded site. Open the URL successful your browser to corroborate that your tract loads correctly, pages work, and images show arsenic expected.

6. Configure a civilization domain and alteration HTTPS

Your tract is deployed and working. However, if you utilized a impermanent domain aliases a subdomain provided by your host, see connecting a civilization domain to springiness your tract a clean, master reside that visitors tin retrieve and trust.

If you already group up a domain name during deployment, you tin skip this step. Your domain and SSL certificate should already beryllium active.

On Hostinger, if you’re utilizing a impermanent subdomain, spell to hPanel → Websites, find your site, and click Connect domain. Follow the on-screen instructions to nexus a domain to your website.

If your domain is registered pinch different provider, constituent it to your host:

1. Open your hosting dashboard and find the domain settings for your deployed site. Your big will show the required DNS records, usually an IP reside and a CNAME value.
2. Sign successful to the work wherever you registered the domain, unfastened the DNS settings, and adhd the records provided by your host.
3. Wait for the changes to return effect. This usually takes 5-30 minutes, but it tin return up to 24 hours. It’s normal if your tract doesn’t load connected the caller domain correct away.
4. Once the domain connects, unfastened your tract successful a browser utilizing the caller reside and corroborate that each page loads correctly.

Most modern hosts, including Hostinger, besides group up SSL certificates automatically aft the domain connects. You should spot the Connection is secure position successful the reside barroom soon aft the domain starts working.

7. Use continuous deployment for early changes

Some hosting providers, including Hostinger, support automatic redeployment. This intends each push to GitHub triggers a caller build and updates your unrecorded tract without requiring you to unfastened the hosting dashboard.

If your supplier doesn’t mention this feature, interaction its support squad to corroborate whether it’s disposable connected your plan.

To verify that automatic redeployment is working:

1. Make a small, visible alteration to your project, specified arsenic editing a heading aliases changing a color.
2. Push the updated codification to GitHub, either by prompting the Antigravity supplier aliases by moving the pursuing commands successful the terminal:

git adhd . git perpetrate -m "Update heading" git push

3. Wait a fewer minutes, past refresh your unrecorded tract successful your browser and corroborate that the alteration appears.

If the update doesn’t appear, unfastened your hosting dashboard and look for a deployment log aliases build history. Most hosting providers show the position of each deployment, truthful you tin spot whether they detected the latest push and whether the build succeeded aliases failed.

If a alteration breaks your unrecorded site, astir providers besides fto you rotation backmost to an earlier deployment. Look for a deployment history aliases erstwhile builds conception successful your dashboard, past redeploy the past moving version.

How to deploy a website from Antigravity to Google Cloud

To deploy a website from Antigravity to Google Cloud, group up the Cloud Run server from Antigravity’s built-in hold store, past punctual the supplier to grip the deployment.

Before you start, instal the Google Cloud CLI connected your computer. Then unfastened a terminal, either your strategy terminal aliases the 1 successful Antigravity IDE, and tally these commands to motion successful and prime your project:

gcloud auth login gcloud auth application-default login gcloud config group task your-project-id

Replace your-project-id pinch your Google Cloud project’s existent ID. The 2nd bid generates the credentials that the Cloud Run server successful Antigravity uses to make API calls connected your behalf.

After authenticating, group up the Cloud Run server successful Antigravity:

1. Open the Agent Manager sheet successful Antigravity IDE and click the … paper astatine the top.
2. Select MCP Servers to unfastened the MCP Store.
3. Search for Cloud Run and click Install.

4. Return to the supplier chat and participate this prompt:

Build and deploy this task to Cloud Run successful my Google Cloud task your-project-id.

5. Approve the terminal commands erstwhile the supplier asks for permission. It will create the required configuration files and tally the deployment.

This method useful good if your app uses Google Cloud services specified arsenic authentication, databases, aliases serverless functions.

Cloud Run is simply a paid work that charges based connected the CPU and representation your app uses while handling requests. It includes a monthly free tier, but costs tin summation arsenic your postulation grows. You tin find the afloat complaint breakdown connected the Cloud Run pricing page.

How to deploy a website from Antigravity via Hostinger Connector

To deploy a website from Antigravity utilizing Hostinger Connector, instal the hold successful your editor, link your Hostinger account, and punctual the supplier to people your task to your hosting plan.

Hostinger Connector is simply a free hold that gives the AI supplier successful your preferred IDE nonstop entree to your Hostinger hosting account. You tin negociate website deployments, domain setup, and server settings done prompts without leaving the IDE.

You only request an progressive Hostinger relationship to get started. However, you’ll besides request an progressive hosting scheme to deploy a website straight from Antigravity to Hostinger.

To group up Hostinger Connector successful Antigravity IDE:

1. Open the Extensions sheet by pressing Ctrl+Shift+X connected Windows aliases Linux, aliases Cmd+Shift+X connected macOS.
2. Search for Hostinger Connector and click Install.
3. Click the Hostinger icon successful the Activity Bar, past prime 1-Click Connect.

4. Complete the browser-based sign-in process. The position badge successful the IDE will move greenish erstwhile you’re connected.

To deploy your project, punctual the supplier pinch your hosting scheme and domain. For example:

Deploy this task to my Hostinger Business hosting scheme connected domain.tld.

Or:

Deploy this fixed tract to immoderate of my progressive Hostinger plans utilizing a impermanent domain.

Hostinger Connector handles the hosting setup and returns the unrecorded URL successful the aforesaid chat window.

After deployment, you tin proceed managing your tract from the aforesaid panel. Try prompts specified arsenic “Connect a domain to my website,” “Show the DNS records for domain.tld,” aliases “Which hosting plans are progressive connected my account?”

Hostinger Connector besides useful pinch different editors. For example, deploying a website from Visual Studio (VS) Code follows a astir identical process because some editors support the aforesaid extensions.

Common Antigravity deployment errors and really to hole them

To hole astir Antigravity deployment errors, cheque whether your host’s build settings lucifer your section setup. Most first-time deployment failures hap because your machine and hosting situation usage different configurations.

The array beneath covers 5 communal issues and really to hole them:

Symptom	Likely cause	Fix
The build succeeds locally but fails connected the host	The big uses a different Node.js type than your computer	Set the Node.js type successful your host’s build settings, aliases adhd an engines section to package.json.
A single-page app shows a 404 correction aft you refresh a page	The big serves fixed files but doesn’t redirect chartless routes to index.html	Add a redirect rule. Use a _redirects record for Netlify, a vercel.json rewrite for Vercel, aliases an .htaccess rewrite norm for Hostinger and different Apache-based hosts.
The big build shows a “Module not found” error	The supplier installed a package locally but didn’t prevention it to package.json	Run npm install <package-name> to adhd the missing package to package.json, past perpetrate package.json and package-lock.json and push them to GitHub again.
The tract shows a blank page aft a successful deployment	The output directory successful the host’s build settings is incorrect	Check the output directory you identified during the accumulation build, past update the host’s configuration to lucifer it.
The tract loads, but API calls fail	Environment variables are missing connected the host, aliases the codification still points to localhost	Add each required variables successful the host’s dashboard and switch hardcoded localhost URLs pinch accumulation endpoints.

If you’re not judge what went wrong, paste the afloat deployment log into Antigravity’s supplier chat and participate this prompt:

This is the deployment log from [host name]. Fix the underlying issue.

The supplier tin trace the correction to circumstantial files, place missing dependencies, and hole the code.

Once you resoluteness the issue, push the hole to GitHub and fto your big redeploy the tract automatically. If you group up Hostinger Connector earlier, you tin redeploy straight from the IDE pinch a punctual specified as:

Redeploy my website connected Hostinger.

Best practices erstwhile deploying a website from Antigravity

Deploying your Antigravity task from the IDE to a unrecorded tract is easier erstwhile you build bully habits into your workflow, specified arsenic utilizing readying mode earlier awesome changes, reviewing the agent’s output earlier pushing, and keeping your limitations up to date.

These habits thief each clip you make changes, not conscionable during the first deployment:

• Use readying mode earlier awesome changes. Without readying mode, the supplier whitethorn commencement penning codification successful a guidance that’s difficult to undo. Start your punctual pinch “Use readying mode to instrumentality [task]” aliases “Write a scheme first. Don’t modify immoderate files yet.” The supplier will create a scheme and hold for your support earlier making changes.
• Review the agent’s changes earlier pushing. The supplier whitethorn accidentally delete files, hardcode values, aliases adhd packages that weren’t portion of your request. Review the changed files each clip the supplier finishes a task. If thing looks wrong, inquire the supplier to explicate aliases revert the change.
• Keep limitations up to date. Outdated packages are a communal vulnerability connected websites. In your GitHub repository, spell to Settings → Advanced Security, past alteration Dependabot alerts and Dependabot information updates. GitHub will automatically unfastened propulsion requests erstwhile a package needs a information update. You tin besides tally npm audit successful the terminal aft each awesome alteration to cheque for vulnerabilities manually.
• Check deployment logs aft each push. A successful push to GitHub doesn’t ever mean the big completed the build successfully. After the build runs, unfastened the deployment log successful your hosting dashboard and corroborate that it succeeded. If it fails, paste the log into the supplier chat and inquire the AI to trace the correction and hole the codification earlier you push again.

Next steps aft your Antigravity tract is live

Once your Antigravity tract is live, group up analytics, monitoring, and backups truthful you’re fresh for existent postulation and protected from information loss.

• Install analytics. Set up Google Analytics aliases Plausible connected your tract truthful you tin spot wherever visitors travel from and which pages they view. Both services supply a codification snippet during signup that you paste into your site’s HTML. Push the updated codification to GitHub and corroborate events look successful your analytics dashboard.
• Add uptime monitoring. Consider adding uptime monitoring to your website to get an alert erstwhile your tract experiences downtime aliases stops responding. You tin do this utilizing a free work for illustration UptimeRobot aliases Better Uptime. Create an account, adhd your site’s URL arsenic a caller monitor, and group it to cheque each 5 minutes.
• Enable backups. This is particularly important for move apps pinch a database, but fixed sites besides use from a speedy rollback action arsenic well. On Hostinger, you tin back up your site connected hPanel by going to Websites → Dashboard → Files → Backups. Other hosts should person a akin action successful their dashboard settings.
• Audit entree tokens. Open the settings aliases API conception of each work you connected during setup (your hosting provider, database, third-party APIs) and cheque for progressive tokens. Remove immoderate you nary longer need, and rotate the ones you’re still utilizing each 3 to six months.
• Upgrade hosting if you deed assets limits. Free-tier hosts headdress build minutes, bandwidth, aliases both. If your tract starts failing builds aliases loading slow nether traffic, unfastened your host’s assets usage dashboard to corroborate you’ve deed a limit, past upgrade to a paid plan. Hostinger customers tin upgrade to a higher-tier plan by going to hPanel → Websites → Upgrade adjacent to the website.

All of the tutorial contented connected this website is taxable to Hostinger's rigorous editorial standards and values.