Managed OpenBerth · EU & US

Your own server, without the server part.

Harbor runs a dedicated OpenBerth instance for you, in the region you pick. Deploy whatever your AI builds. No configuration. No command line unless you want one.

Start a free 14-day trial → See how it works
Your workspace
Budget Tracker
StatusReady
RegionEU · West
Deployments3 live
Sandboxes1 paused
AdminManaged for you
Deploy with one clickNo card to tryStored in EU or USOpen-source compatibleBuilt on OpenBerthDeploy with one clickNo card to tryStored in EU or USOpen-source compatibleBuilt on OpenBerth
§1  What you get

A dedicated place to run the things you already build with AI.

01

A real server, without running one.

Each workspace is its own isolated OpenBerth instance. Not shared. Not simulated. We handle keeping it alive, updated, and reachable.

02

A dashboard built for people, not operators.

Deploy apps, run sandboxes, manage secrets — all from a clean interface. No terminals, no YAML, no ops vocabulary.

03

An escape hatch when you want one.

Technical users can create access keys and use the open-source OpenBerth CLI directly. Nothing's locked in, nothing's hidden.

§2  How it works

Four unremarkable steps between you and a running workspace.

i

Sign in with Google.

No forms. No password to invent. You're in. We create your account and start your 14-day trial — no card required.

~ 5 seconds
ii

Name your workspace, pick a region.

Call it something you'll remember — Budget Tracker, Side Project, The Family Cookbook. Choose where it lives: Europe or the United States.

~ 10 seconds
iii

We set up your OpenBerth.

A dedicated server is provisioned, configured, and handed to you. It's instant. By the time you look up from your screen, it's ready.

~ 2 seconds
iv

Deploy whatever you've made.

Drag in a project. Connect your AI tool. Or open the terminal if you know what that is. Either way, it just works — and you haven't seen a config file yet.

As long as you need
§3  What's inside

Everything OpenBerth offers, surfaced through something you'd actually use.

A / Deployments

Ship what you built. See it live.

Create, update, and retire deployments from the dashboard. Inspect logs. Lock stable versions. Protect with passwords or allow-lists. Everything OpenBerth's admin API can do, minus the API part.

  • Create from uploaded code or AI output
  • Live logs and build output in the dashboard
  • Lock a deployment to prevent accidental changes
  • Set access control: public, password, or allow-list
B / Sandboxes

Iterate fast. Promote when ready.

Sandboxes are throwaway environments with hot-reload. Test changes instantly, then promote the one that works into a proper deployment. Everything else is forgotten.

  • Instant file push with hot reload
  • Run one-off shell commands
  • Install dependencies without rebuilding
  • Promote a sandbox into production with one click
C / OpenBerth users

Credentials the workspace owns.

Create named OpenBerth users for different purposes — your laptop, a deploy bot, a CI script. Rotate their keys when you need to. Delete them when they've served their use.

  • Create users without leaving the dashboard
  • Rotate or revoke keys at any time
  • Deletion is guarded — can't accidentally orphan resources
  • Admin credentials stay with us, never exposed
D / Secrets

The things you don't put in code.

Keep API keys, database URLs, and other secrets in one place. Scope them to a single user, or share them across the workspace as globals. Injected at deploy time, encrypted at rest.

  • Per-user or workspace-wide scope
  • Never rendered in the UI once saved
  • Updated values restart everything that uses them
E / CLI access

For when the terminal feels right.

The open-source OpenBerth CLI works unmodified against your managed instance. Same commands, same behavior, same muscle memory. No Harbor-specific tool to install.

  • Generate a key in the dashboard, paste into the CLI
  • Every OpenBerth command just works
  • Your workflow stays portable if you ever self-host
F / Workspace health

We tell you what's going on, in plain words.

Your workspace has a state — and you'll always know what it is without decoding logs. Emails when something needs attention. Live updates when something's changing.

  • Clear labels: Ready, Setting up, Paused, Having trouble
  • Live refresh during transitions — no F5 needed
  • Emails for things that matter, silence for things that don't
The only four states you'll ever see
Ready
Your workspace is running and reachable. Use it.
Setting up
Almost there. Usually takes a second or two.
Paused
Temporarily stopped. We'll tell you why and what to do.
Having trouble
Something needs attention. You'll get an email with details.
§4  Pricing

Start free. Pay when it's actually useful to you.

Trial
€014 days
Everything you need to decide. No card required.
  • 1 workspace, any region
  • All dashboard features
  • Email support
  • Ends after 14 days unless you upgrade
Start trial
Hobby
€9per month
For personal projects and small side projects. Hosted in the EU.
  • 1 workspace, EU region
  • Everything in the dashboard
  • CLI access via OpenBerth users
  • Email notifications
  • Cancel anytime
Choose Hobby
Pro
€29per month
For people running a few things. EU or US, your pick.
  • 5 workspaces
  • EU and US regions
  • Custom domains
  • Priority email support
  • Upgrade or downgrade any time
Choose Pro
Prices shown are indicative. Final plan structure will be set before launch.
§5  Questions

A few things worth asking.

Is this just OpenBerth with a wrapper? +
Yes, and that's the point. OpenBerth is an excellent open-source project. Harbor runs it for you, on dedicated infrastructure, with a dashboard that doesn't require you to read documentation first. Your workflow stays portable — if you ever want to self-host, your apps and configurations move with you.
What happens when my trial ends? +
You'll get emails three days before, on the last day, and when it ends. If you don't upgrade, your workspace is paused — not deleted. You get a 14-day grace period to upgrade and resume, after which the workspace is removed. Nothing is deleted silently.
Where does my data live? +
You pick when you create a workspace: Europe (EU-West) or United States (US-East). The workspace and everything in it stays in that region. We don't replicate across continents.
Can I use the OpenBerth CLI? +
Yes — the open-source CLI, unmodified. You create an OpenBerth user in the dashboard, get a key once, paste it into the CLI. Every command in the OpenBerth docs works against your managed instance.
What if OpenBerth changes something and breaks my workflow? +
We test OpenBerth upgrades against the platform before rolling them out. If a breaking change lands, we give you notice and a migration path. The goal is that you never have to think about OpenBerth version management.
Can I cancel and take my apps elsewhere? +
Your deployments are regular OpenBerth deployments. The project files are yours. Cancel anytime, export what you need, run it on your own OpenBerth instance. We don't lock you in because we can't — the underlying project is open source.
I'm not a developer. Is this for me? +
If you use AI tools that build things — apps, websites, scripts — and you've wanted somewhere to actually put them, yes. The dashboard is designed for you first, with everything that matters reachable without a terminal or config file.

Start free. See if it fits.

Sign in with Google →
14 days · No card · 5 seconds to sign up