Skip to content
PORTWAYS
System statusUptime & incident updates
BUILT & RUN BY GAURAV / SUVO

Portways is my private, self-hosted platform for deploying and running applications.
I built it to manage my projects on hardware I own.

Explore the project See how it works

A personal project. No public sign-ups.

Portways / new deploymentINTERACTIVE EXAMPLE

Inside a deployment.

An example of the platform’s workflow.

REPOSITORY URL
github.com/example/project
mainAuto-detect build
This is a demo. It won’t deploy a real app.
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.

The tools I use to deploy applications and keep them running.

01

Deployments from Git.

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

02

Apps, databases, and storage.

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

Resource controls.

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

05

Rollback when a launch fails.

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

06

Public service status.

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

FROM REPO TO RUNNING

How the pieces
come together.

Every deployment starts with code and ends with a running container. Portways handles the steps in between.

More about the project
Running on my own hardware.

I manage the servers as well as the software that runs on them.

  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
SERVICE STATUS

See what’s online.

Check uptime, recent incidents, and planned maintenance
on the Portways status page.

View system status
A FEW MORE THINGS

Good to know.

Have another question?
Read all FAQs

What is Portways?

Portways is the private platform I built to deploy my applications and manage their databases and servers. It runs on my own hardware. I’m Gaurav, also known as Suvo, and this is one of my biggest projects.

Is this a public hosting service?

No. I use Portways for my own projects. This site explains what I’ve built; there are no public hosting plans or sign-ups.

ABOUT THE BUILDER

I’m Gaurav. You can call me Suvo.

Portways is one of my biggest projects. Happy to talk about it.

Get in touch For project questions or just to say hello.