Skip to content
Menu
StudiosWorkflowClientsPortfolioBeta scopeSign in

Private beta · client-site deployment

Hosting built
around your clients.

One workspace for the websites you are responsible for. Build from GitHub, review the release, then decide what goes live.

Request beta accessSee the workflow
VeynodeStudio workspacePrivate beta
Client A / Product siteProduction live

Product site

Client A · GitHub · main

Production

Live
#dep_41ad0e
34bc128 · 12 min agoproduct-a1b2c3d4e5f6478899aabbccddeeff00.sites.veynode.app

Preview

Ready
#dep_83c921
8f2e7a4 · just nowPublish deployment

Production is unchanged. Review this release before publishing.

Build 8f2e7a4Artifact verifiedRollback available
  • GitHub source
  • Vite + static sites
  • Explicit publish

Who it is for

The work is the client site,
not the server.

Veynode is hosting for agencies and freelancers who ship modern client websites from GitHub. The workspace is organized around the client relationship and the release in front of you.

Studios

Keep a portfolio of client websites in one workspace. Each site stays attached to its client, repository, and current deployment.

Freelancers

Use the same path for every engagement. Build from GitHub, review the deployment, and publish when the release is ready.

Small teams

See what is live, what is waiting, and what failed. The release stays explicit, and the infrastructure stays behind the product.

01 — Release control

Build is not
production.

Every change gets a place to land before it touches the live route. Veynode keeps the release gate visible.

  1. 01Build

    Artifact verified

    The build runs from the GitHub repository and its committed lockfile. A succeeded build produces an immutable artifact.

    Succeededcommit 8f2e7a4
  2. 02Preview

    Release ready

    That artifact becomes a deployment with its own URL. Opening the preview does not change the live route.

    Readyimmutable URL
  3. 03Review

    Production unchanged

    The current production deployment stays in place. Nothing goes live until you choose to publish.

    Awaiting reviewexplicit approval
  4. 04Publish

    Make it live

    Publishing makes that deployment the live route. A previous ready deployment remains available for rollback.

    Liverollback available
BuildPreviewReviewPublishNo automatic production cutover

02 — Client model

Every client.
Every site.
One workspace.

Project lists are useful for infrastructure. They are not enough for the people accountable for a portfolio of client websites.

Your client relationship is part of the product model, not a spreadsheet beside your hosting provider.

Studio workspace03 clients / 06 sites
  1. Client A02 sites
    • Product siteLivedeployment #dep_41ad0e
    • Campaign sitePreviewdeployment #dep_98c12d
  2. Client B01 site
    • Marketing siteLivedeployment #dep_22aa91
  3. Client C02 sites
    • DocsNeeds attentiondeployment #dep_71bd02
    • StorefrontPreviewdeployment #dep_8c310a

03 — Portfolio

Know what needs attention.

Launch is a moment. The workspace is where you keep the rest of the work legible.

See what the beta supports

Client sites

Client · site · deployment state

Client / siteStateDeployment
Client AProduct siteReady for review#dep_83c921
Client BMarketing siteLive#dep_22aa91
Client CDocsNeeds attention#dep_71bd02
  1. Live

    A published deployment is serving the site.

  2. Ready for review

    A newer deployment is waiting. Production is unchanged.

  3. Build failed

    The latest build did not produce an artifact to publish.

  4. Setup required

    The site does not have an authorized repository yet.

  5. Not published

    A deployment may exist, but nothing is live.

  6. Healthy

    The live site has no newer release waiting.

After the release

The record stays readable.

A published site does not collapse into a host. The workspace keeps the facts you need the next time you open it.

  1. 01Client

    Which client the site belongs to.

  2. 02Commit

    The commit that was built.

  3. 03Build

    Whether that build succeeded.

  4. 04Live

    Which deployment is serving production.

  5. 05Waiting

    Which deployment is ready and not yet published.

  6. 06Rollback

    A previous ready deployment can be restored.

04 — Beta boundary

Narrow by design.
Clear about the boundary.

Veynode currently focuses on Git-based frontend projects that produce a static artifact. That focus is intentional while the deployment path is being proven.

Supported today

Projects
Static HTML, client-side Vite, and Cloudflare Vite Build Output v0 projects with one supported default Worker, including supported SSR output.
Source
GitHub repositories authorized through the Veynode GitHub App.
Packages
npm or pnpm with one committed lockfile.
Release
Preview, explicit publish, and rollback to a ready deployment.

Not in this beta

Runtimes
Long-running servers, containers, PHP, WordPress, custom Worker bindings, or outbound requests.
Data
Managed databases, Redis, and persistent application services.
Automation
Automatic production changes on Git push.
Domains
Custom-domain management in the beta control plane.

Bring one real
client site.

  • ProjectA Vite application, or a repository with a root index.html.
  • Packagesnpm or pnpm, with one committed lockfile.
  • SourceA GitHub repository you can authorize.

Test the complete path from repository to reviewed, published, recoverable website.

Request beta accessBest fit: Vite or static frontend projects