Skip to content

Workflow

Repository in. Live app out.

The whole loop - connect a repo, build it, put it on a URL, attach a database and auth, then keep shipping - without assembling a pipeline first.

Start building See the infrastructure

Four steps

From push to production.

  1. 01

    Connect

    Point glashDB at a GitHub repository or push a folder straight from the CLI. We detect Next.js, Nest, Vite, Express, Remix, static sites, and the common Python frameworks - no config file to write.

  2. 02

    Build

    Your project builds inside its own container on a hardened host. Install, build, and package all stream back as logs, and a diagnoser translates the usual failures into something you can act on.

  3. 03

    Go live

    The build is published behind nginx at your-slug.glashdb.com with SSL already issued. Attach a custom domain whenever you are ready and the edge route follows.

  4. 04

    Wire the rest

    Attach a Postgres database and DATABASE_URL lands in the runtime. Turn on glashAuth for sign-in, sessions, and roles. Neither one needs a second vendor.

Surfaces

Dashboard, terminal, or agent.

CLI

glash, from your terminal

Log in once, then deploy, tail history, manage environment variables, and roll back without opening a browser.

$ npm i -g @glash/cli
$ glash login
$ glash deploy
CLI reference
MCP

Or let your agent do it

Drop the glashDB MCP block into Cursor, Windsurf, Claude Code, Codex, Kimi, or Antigravity and ask for a deploy. The build streams back into the chat.

"mcpServers": {
  "glashdb": {
    "command": "npx",
    "args": ["-y", "@glashdb/mcp"]
  }
}
Copy the MCP config

Day two

The first deploy is easy. The next hundred matter more.

Ship a change

Push again, or run glash deploy. The new build replaces the old one and the route flips when it is ready.

Roll back

Every previous build stays available. Pick one and it boots again - from the dashboard or the CLI.

See what happened

Deployment history, build logs, auth events, and admin actions are recorded per project.

Move an existing app in

One-click migration brings source, environment variables, and integrations across from Vercel.

Prefer a framework that already knows the platform?Meet GlashJS

Prompt it. Build it.
Ship it.

Start building Launch app