Skip to content
PORTWAYS
ONE OF MY MAJOR PROJECTS · GAURAV / SUVO

Portways is my private, self-hosted platform for deploying and running applications.
Built from the ground up. Operated on my own hardware.

Explore the project See how it works

A personal project showcase · Privately operated

Portways / new deploymentINTERACTIVE EXAMPLE

Inside a deployment.

An example of the platform’s workflow.

REPOSITORY URL
github.com/example/project
mainAuto-detect build
Illustrative preview. No repository is deployed.
DEPLOYMENT PIPELINE main
  1. Clone repositorydone
  2. Detect environmentdone
  3. Build applicationdone
  4. Start containerdone
Example application is live.example-project.portways.app
SUPPORTED ENVIRONMENTS
Next.jsNode.jsPythonDockerStatic sites
THE SYSTEM, IN MOTIONSELECT A STAGE TO EXPLORE
02 / 04

From source to a running application.

Portways identifies how a project should build, prepares it, and records progress in deployment logs.

THE PLATFORM

What I built
into Portways.

Deployment, data, routing, and visibility in one private platform.
Here’s what sits behind the name.

01

A complete deployment pipeline.

Repository URLs, GitHub integration, and a dedicated Git remote feed into one build pipeline, with logs and deployment history.

02

A home for the whole stack.

The platform runs Node.js, Python, static sites, and Dockerfile-based applications, with managed Postgres, Redis, and S3-compatible storage.

03

Routing, domains, and HTTPS.

Applications receive a portways.app subdomain. Custom domains are supported, with routing and HTTPS handled by the infrastructure.

04

Infrastructure under my control.

Per-project resource limits, scaled workloads, and cluster management bring the operating side of the platform into one place.

05

A safer next deployment.

If a new container crashes on startup, Portways restores the previous working image. Build logs make the failure visible.

06

Visibility beyond the dashboard.

A dedicated public status page brings together service availability, incident updates, and scheduled maintenance.

FROM REPO TO RUNNING

How the pieces
come together.

The core of Portways is a repeatable path from source code to a running container. This is how the private platform handles a deployment.

More about the project
Real hardware. Direct ownership.

Built and operated by Gaurav (Suvo), on hardware he owns and manages.

  1. 01

    Source code comes in

    Source arrives from a repository URL, a private repository through a connected GitHub App, or a push to a Portways Git remote.

    repository → main
  2. 02

    The platform builds it

    Portways detects the environment or uses the repository’s Dockerfile. Build logs stream internally as the application image is created.

    clone → detect → build
  3. 03

    The application goes live

    The running container receives a portways.app address. Routing, custom domains, resource settings, and subsequent deployments stay in the same system.

    example-project.portways.app
OUT IN THE OPEN

A clear view of the network.

Service availability, incident history, and maintenance updates.
Follow what’s happening on the dedicated Portways status page.

View system status
A FEW MORE THINGS

Good to know.

Have another question?
Read all FAQs

What is Portways?

Portways is a private, self-hosted platform-as-a-service built and operated by Gaurav (Suvo). It brings application deployments, databases, and infrastructure management into one dashboard, on hardware he owns and manages. It is one of his major personal projects.

Is this a public hosting service?

No. Portways is private infrastructure. This website is a showcase of what Suvo built and an explanation of how it works. It does not offer public registration or hosting plans.

PERSONALLY BUILT. PERSONALLY OPERATED.

Portways, by Suvo.

One of my major projects. A look at what I’ve built.

Get in touch Private infrastructure. Shared here as a project showcase.