For developers · hardware you own · your own domain

Your own addresses

You don't need a third-party cloud account to put something on the internet. A phone, a Raspberry Pi or the laptop in front of you. One Viaalink Relay. Your own domain. That is the whole stack.

Made in the Netherlands 🇳🇱 🇪🇺 · Runs on Linux, macOS, Docker and NAS · Open app registry

Who it's for

Three ways people use it.

  • Web developers

    via expose 3000 gives a port on your machine a public HTTPS address through your Viaalink Relay.

    The Viaalink CLI
  • Agencies & web hosts

    Host sites and tools for customers on their own domain. Partner terms on the license, on request.

    Partners
  • DevOps & CI/CD

    In a pipeline, the runner connects to your Viaalink Relay with its own SSH key. via expose gives the app your job started an HTTPS address on your domain for your tests and reviewers, and via expose stop takes it away when the job is done.

    Using via in CI/CD

How the system works

One Relay, your own domain, and every device behind it.

Your devices connect out to one Relay. The Relay holds your domain and sends every visitor to the right device. Pick where the Relay lives, then send a request and follow it.

  1. A visitortypes git.kelvin.example
  2. DNS*.kelvin.example → Relay
  3. Your home
    1. Your routerforwards 443 to the Relay
    2. Viaalink Relayholds the domain and HTTPS
      • Phone · Notetaker notes.kelvin.example
      • Raspberry Pi · Gitea git.kelvin.example
      • Laptop · your project dev.kelvin.example

Follow one request from a visitor to Gitea on your Raspberry Pi, and back.

  1. 01 Your devices

    A phone, a Raspberry Pi, the laptop you build on. They stay behind your router, without a public address of their own.

  2. 02 One Relay

    One machine that stays on holds your domain and the HTTPS certificates. At home your router forwards 80 and 443 to it. On a VPS nothing is forwarded.

  3. 03 Devices connect out

    Each device keeps one connection open to the Relay. No port forwarding per device, and it works from a café or a train.

  4. 04 A name for each

    notes, git and dev.kelvin.example: one domain, as many names as you have devices.

  5. 05 Visitors go through the Relay

    The Relay reads the name and hands the request down the right connection. HTTPS all the way.

  6. 06 Publish more

    via up publishes the services in your project file. via expose 8080 publishes one port. Same Relay, new names.

The full Relay walkthrough Previews for your branches with the via CLI

Cloud or your own hardware

The cloud rents you a computer. You already have one.

An honest comparison. The cloud is faster to start, and someone else keeps it running. Most other things favour the machine on your desk.

A white server cabinet, full of rack servers, seen from a distance.

A bill every month

Cloud platform
A small grey home server with its status lights on.

Paid once

Your hardware + a Relay
Cloud platformYour hardware + a Relay
What you payA monthly bill that grows with use and with every user.The machine once, a domain name, and one Relay license per year.
Where your data isTheir datacenter, their region, their terms.In your room. You can point at it.
When you stop payingYour project goes offline. Export what you can.The machine and everything on it are still yours.
Your addressproject.platform.app, until the platform changes.name.yourdomain, for as long as you hold the domain.
What you learnTheir console.Linux, Docker, DNS, HTTPS. Skills that transfer.
Who keeps it runningThey do. Outages are theirs to fix.You do. If the machine is off, the site is off.

If you never want to think about a machine, use the cloud. If you want to own the thing you built, keep reading.

Inspiration

Machines that can do one of two jobs.

Relay

The machine runs your Viaalink Relay: the front door that gives your devices an address on your domain.

Services & apps

The machine runs your websites, services and apps. They reach the world through a Relay, at home or in the cloud.

Your first Relay

Four steps, in the order you'll do them.

Start with what is on your desk. A new Relay runs 14 days without a license; after that, Free is one e-mail sign-in away.

A hand slides a hard drive into a small home server.
  1. 01

    Pick a machine that stays on

    A Raspberry Pi, a mini PC, an old laptop, a NAS. amd64, arm64 or armv6.

  2. 02

    Get a domain name

    Any registrar. Point it at your home connection, or at your VPS.

  3. 03

    Install the Relay

    Linux service, Docker Compose or the NAS app. Your router forwards 80 and 443, or the VPS does it for you.

  4. 04

    Connect a device

    via expose 3000 on your laptop puts your first project on your domain. Then add the phone, then the Pi.

What it cannot do

Said first, so you can decide.

We would rather you know this before you start than after.

  1. 01It does not make a Raspberry Pi faster than a datacenter. A busy site needs a bigger machine.
  2. 02If your machine is off, your site is off. Keeping it on is yours to do.
  3. 03You still need a domain name, and either a router you can configure or a small VPS.
  4. 04Free needs an e-mail sign-in on viaalink.com. We use it to see who runs a Relay and to stop abuse, not to mail you.
  5. 05The Relay is one more program to keep updated. It runs on your machine, so that is your job.
  6. 06Notetaker runs on Android, Windows (alpha), macOS and Linux. iOS is coming.

Roadmap

What we are building.

Viaalink Relay, the via CLI and the developer platform: what is being built now, what comes next and what is further out. No dates. Something is done when it is in a public release.

Being built now

See the roadmap

Contact

Talk to a human. Kelvin is one.

Questions about Viaalink Relay or the CLI? Write directly.