Bring your project
Choose a repository or project source. GitHub is planned as an initial connection, with more sources to follow.
In development · not accepting deployments yetDeploy with GigaTools.
Website deployment for Pro
Deploy with GigaTools.
Connect the hosts you already use.
We’re building one workspace for two ways to ship: deploy a supported project directly with GigaTools, or connect an external hosting provider. Keep preview status, release context, and launch checks beside the project you’re building.
Availability: direct deployment and provider connections are in development. Supported destinations, build limits, and resource caps will be published before public access opens.
One deployment workspace
Bring a project. Choose a destination. See what shipped.
The planned flow connects your source, destination, and release checks without losing project context.
Choose how to deploy
Use direct GigaTools hosting for a supported front-end build, or connect a supported provider you already use.
Review the release
Track build and deployment status, open a preview when available, and return to your workspace for launch checks.
Two ways to ship
Choose the destination that fits your project.
Direct deployment will publish a supported front-end project through GigaTools. Provider connections will bring deployment status and release context from external hosts into the same workspace. Your project stays the center of the workflow, whichever destination you choose.
The preview limits below apply only to GigaTools-hosted projects. An external provider continues to set its own hosting plan, resource limits, and retention rules. We will name supported provider connections before launch rather than implying every host is already available.
Direct GigaTools hosting
The planned Pro allowance is five active hosted previews for supported static front-end builds.
Provider connections
Connect a supported external host to bring deployment context into the project workspace. Available providers will be listed before launch.
30 days, extend once
Each GigaTools-hosted preview starts with 30 days. One renewal can extend it to 60 days total.
Project sources
GitHub is planned as an initial repository source. Additional sources can be added as the deployment workflow expands.
What gets removed at expiry?
Expiry applies only to a GigaTools-hosted preview: its temporary checkout, generated artifacts, and preview URL. Your source repository stays with its provider. GigaTools will show the expiry date and provide advance notice before a hosted preview is removed. Connected external deployments follow their provider’s own retention rules.
How will direct builds be protected?
Direct builds run project code supplied by users. The GigaTools-hosted worker is planned for infrastructure separate from the main app, with isolated execution and resource limits. The service will open only after those controls, cleanup, and monitoring are in place. Connected external providers run their own builds under their own infrastructure and terms.
Who is this for?
This workflow is for developers and teams that want release context in one place. Use direct GigaTools hosting for a short-lived front-end preview, or connect a supported provider for the infrastructure your project already uses. Always-on servers, background jobs, and databases are outside the initial GigaTools-hosted preview scope.
While deployment connections are being built, you can still use the project workspace, run a website launch audit, check page speed, and review the Pro workspace plan.
Clear before launch
Deployment and hosting: common questions
We will publish supported providers, frameworks, and direct-hosting resource limits before deployment opens.
Can I deploy a website from GigaTools today?
Not yet. Direct deployment and hosting provider connections are in development. We will open deployment only after the supported destinations, build limits and hosting infrastructure are ready.
Can I connect my existing hosting provider?
That is part of the planned workflow. You will be able to connect supported providers and manage deployment context from your GigaTools workspace. We will publish the first supported providers before launch.
What does direct deployment include?
The first GigaTools-hosted release is planned for static websites and front-end projects that produce static build output. Always-on servers and managed databases are outside the initial direct-hosting scope.
Which code sources will be supported?
GitHub repositories are planned as an initial source. The hosting workflow is designed to support additional sources as integrations are added. We will list available connections before launch.
How many GigaTools-hosted previews can I create?
The planned Pro allowance is up to five active GigaTools-hosted previews. Each lasts 30 days and can be renewed once, for a maximum of 60 days. These limits do not change the terms of external hosting providers.
Will an expiring preview delete my source repository?
No. Expiry removes only the GigaTools-hosted preview and temporary build copies. Your source repository remains with its provider. External provider deployments follow that provider’s own retention rules.
Where will direct builds run?
The direct-deploy worker is planned for infrastructure separate from the main GigaTools application. It will open only after isolated builds, resource limits and cleanup are configured and tested.
Keep your next release in one place.
Use the GigaTools workspace now. Direct deployment and provider connections will open after the integrations and hosting service are ready.