Gigadrive Network

Gigadrive Network is a European serverless platform for Node.js, PHP, and Bun applications. Point it at a project directory or a Git repository: it runs the build, serves the result as Functions and static assets, and puts a CDN in front.

Your first deployment

1. Install the CLI

   npm install -g gigadrive

   The package installs two commands, gigadrive and the shorter alias gn. It needs Node.js 20 or newer.

2. Sign in

   gigadrive login

   The terminal prints a code and opens your browser so you can approve the login. Credentials are stored on your machine, so this is a one-time step.

3. Deploy the directory you are in

   gigadrive deploy

   If the directory is not linked to an application yet, the CLI creates one, saves the link in .gigadrive/project.json, and deploys it. It then polls once a second, printing every status change and every new build log line until the deployment finishes:

   Creating deployment...
   Deployment ID: 0197b2f1-2f4a-7a0b-8a2d-222222222222
   Creating archive...
   Archive created (2.14 MB)
   Uploading archive...
   Upload complete.
   The deployment pipeline is now being provisioned. This may take a few seconds.
   Status: Pending
   Status: Queued
   Status: Building
   Status: Provisioning
   Status: Active
   Deployed to https://my-app-k3n8q2wp.gigadrive.app

The hostname on the last line belongs to that one deployment and never moves. An upload deploy like this one lands in the Preview environment, so the usual next step is Connect a repository: pushes then deploy on their own, and a stable production URL follows the newest production deployment.

What happens without a config file

Nothing in the preceding example is configured. The build runs the build script from your package.json if there is one, and matches the project against thirteen framework definitions to work out the entrypoint, the static asset directory, which runtime it needs, and how much memory each Function gets. A standalone Next.js build becomes a single Function with at least 1024 MB.

Every application starts with two environments. Production tracks the branches main and master, and Preview takes every branch no other environment claims. Each deployment also gets a permanent hostname of its own under gigadrive.app, which keeps serving after a newer deployment takes over the production alias.

Every framework default is overridable in gigadrive.yaml, documented under Configuration.

Programmatic access

The console is one surface among several. Applications, deployments, environment variables, file storage, and AI Gateway are all reachable from the CLI, the SDK, and the REST API at api.gigadrive.network.

Code running inside a deployed Function needs no stored key for any of that. The platform injects GIGADRIVE_CLIENT_ID and GIGADRIVE_CLIENT_SECRET when the Function starts, and the SDK picks them up on its own. OIDC federation covers how those credentials are issued and what they are allowed to do.

Sections