Oblien (@OblienHQ) header
Oblien (@OblienHQ) profile picture

Powerful, flexible machines for humans and agents. Temporary, persistent, or serverless

Kernel
Joined February 2025
Photo by Oblien (@OblienHQ)Photo by Oblien (@OblienHQ)Photo by Oblien (@OblienHQ)Photo by Oblien (@OblienHQ)Photo by Oblien (@OblienHQ)Photo by Oblien (@OblienHQ)Photo by Oblien (@OblienHQ)Photo by Oblien (@OblienHQ)Photo by Oblien (@OblienHQ)Photo by Oblien (@OblienHQ)
Oblien retweeted
Ladies and gentlemen, it's finally here. OpenShip v1.0.0 is officially out 🔥 OpenShip is now production-ready, built to handle your production workloads and scale with even the most demanding applications.
6
13
4
236
10,541
You can get it from oblien dashboard
in desperate need of macOS sandboxes am I the only one ?
5
295
Day 4/30: VM-to-VM Connections With Oblien, connecting VMs/Sandboxes is incredibly easy. You can create a role in seconds and allow any VM to communicate with other VMs over the internal network. Unlike traditional VPS/VMs providers, where you have to manually configure networking, firewall rules, and access between servers, Oblien makes it a one-click configuration. For example, you can run an AI agent on one VM and give it access to another VM where your databases, tools, or workloads are running and it controls it end to end. No complicated networking setup. Just define the role, connect your VMs, and let them work together. That's how simple infrastructure should be.
Day 3/30: macOS workspaces Need a Mac to build an iOS app? Most cloud sandboxes stop at Linux. On Oblien, pick macOS from the image list. Terminal, files and commands run inside macOS, through the same API as any workspace. Your agent can have a Mac too.
2
5
670
Oblien retweeted
We've added a cool feature in the latest OpenShip version (v0.9.12+) Meet Virtual Routes 🚀 You can now define custom routes at the edge and fully customize their responses. For example, if you've already deployed your app and forgot to add a verification challenge endpoint (like a URL verification file), you don't need to change your code or redeploy. Just create a virtual route, define its path, response type, and content, and it's instantly available. Simple, flexible, and no redeployment needed.
2
60
2,505
New landing page with the correct branding
1
3
1
47
2,490
Oblien made the OpenShip Cloud journey incredibly effortless. Thanks to Oblien Namespaces, every user gets their own quotas and resources through simple API configuration, with no heavy lifting required. They don’t have to worry about managing user isolation or infrastructure themselves. We handle all of that for them. That’s why Oblien is the right choice.
We've added a 99% SLA to all cloud plans. This means we'll compensate any user affected by service disruptions. We've also added 20% off all plans for anyone looking to migrate to the cloud. Use code: MIGRATE
1
4
439
Oblien might be OpenSourced ?
What do you guys think? Should we ruin this YC race of 5,000 new sandbox startups and open-source Oblien? Oblien is our super sandbox provider and infrastructure company, so we're ready. It's literally one click away from open-sourcing it and linking it to self-hosted OpenShip... Oh god this would be super cool, especially with OpenShip's autoscaling feature. All you need to do is add new servers.
2
384
Move to your own servers. Nothing beats owning your infrastructure.
Ladies and gentlemen, Introducing Railway and Vercel migration to OpenShip Both self-hosted and cloud customers can now migrate their databases, apps, APIs, and workloads directly from Railway and Vercel to their own servers with just a few steps. Get started: Install OpenShip v0.9.12 or later, or update your existing installation. And we're just getting started. Coming next: Heroku, Render, Fly io, Supabase, Neon, MongoDB Atlas, PlanetScale, Upstash, Redis Cloud, Netlify, DigitalOcean App Platform, and more. We'll keep expanding our migration capabilities to help you move away from virtually anything on the INTERNET. See the demo below 👇
2
9
463
Oblien retweeted
Ladies and gentlemen, Introducing Railway and Vercel migration to OpenShip Both self-hosted and cloud customers can now migrate their databases, apps, APIs, and workloads directly from Railway and Vercel to their own servers with just a few steps. Get started: Install OpenShip v0.9.12 or later, or update your existing installation. And we're just getting started. Coming next: Heroku, Render, Fly io, Supabase, Neon, MongoDB Atlas, PlanetScale, Upstash, Redis Cloud, Netlify, DigitalOcean App Platform, and more. We'll keep expanding our migration capabilities to help you move away from virtually anything on the INTERNET. See the demo below 👇
We're bringing one-click migration from Vercel and Railway to OpenShip in the next release. We've already built this for server-to-server and other control planes migrations, so we're extending the same experience to make moving from Vercel and Railway just as easy.
9
7
4
80
6,222
This is exactly what Oblien does for agents
I was wrong about agent sandboxes. In my article I said pattern 1, where the agent runs on your infra and only calls a sandbox for tools, doesn't work at scale. I moved everything to pattern 2 and put the whole agent inside a VM. At the time that made sense but today I'd pick pattern 1. For your own personal agent, a coding agent, or a small project, isolating the whole agent in a VM is still a great default. I would keep doing it. At real multi-tenant scale it falls apart. There will be more agents than humans. Every human gets one computer. Giving every agent its own VM running 24/7 means billions of CPU-hungry machines, and we're already short on compute. Most of what an agent does doesn't need a machine at all. It thinks, calls APIs, reads pages, and waits. Nobody needs a 4 CPU VM sitting idle so an agent can run a simple JS script once an hour. What I'd build now: > the agent loop runs on shared infra that scales > it gets a sandbox only when it has to run untrusted code > sandboxes spin up in seconds and die right after > zero state on the machine, everything lives outside it VMs are a tool the agent calls, but they shouldn't be where it lives.
1
136
Day 3/30: macOS workspaces Need a Mac to build an iOS app? Most cloud sandboxes stop at Linux. On Oblien, pick macOS from the image list. Terminal, files and commands run inside macOS, through the same API as any workspace. Your agent can have a Mac too.
Day 2: Sleep when idle Your VM doesn't need to keep running when it's not being used. And you shouldn't have to miss a single request because of it. Set a rule to automatically put your VM to sleep when idle. Oblien saves its memory to disk and releases the compute, so you stop paying for idle resources. The moment a new request comes in, it wakes up and continues right where it left off. Whether it's your app, workload, or AI agent.
1
1
8
917
Day 2: Sleep when idle Your VM doesn't need to keep running when it's not being used. And you shouldn't have to miss a single request because of it. Set a rule to automatically put your VM to sleep when idle. Oblien saves its memory to disk and releases the compute, so you stop paying for idle resources. The moment a new request comes in, it wakes up and continues right where it left off. Whether it's your app, workload, or AI agent.
Oblien lets you run any image, including standard Docker images, inside hardware-isolated MicroVMs instead of regular containers. Each VM gets its own kernel and isolation boundary while remaining lightweight. You get the best of both worlds: keep using your existing Docker images and workflows while benefiting from much stronger isolation. This is what allows platforms like @openshipio to run their cloud infrastructure with each customer's workload isolated in its own VM, while still taking full advantage of the existing container ecosystem.
1
1
1
8
737
Oblien lets you run any image, including standard Docker images, inside hardware-isolated MicroVMs instead of regular containers. Each VM gets its own kernel and isolation boundary while remaining lightweight. You get the best of both worlds: keep using your existing Docker images and workflows while benefiting from much stronger isolation. This is what allows platforms like @openshipio to run their cloud infrastructure with each customer's workload isolated in its own VM, while still taking full advantage of the existing container ecosystem.
We're starting a 30-day challenge. 30 days to show you what Oblien can do and just how flexible it is compared to other solutions. Every day, we'll highlight a different feature and show you how it can make a difference in your workload.
2
1
1
12
1,288
We're starting a 30-day challenge. 30 days to show you what Oblien can do and just how flexible it is compared to other solutions. Every day, we'll highlight a different feature and show you how it can make a difference in your workload.
1
6
997
Sandboxes shouldn't be temporary by design. At Oblien, we built flexible sandboxes that you can turn into persistent workspaces with just one click. Imagine your sandbox isn't just something you spin up temporarily, but something that can also run 24/7, be turned off whenever you want, or even converted into a fully serverless environment that wakes up on the first request. All of this, with VM-to-VM networking, desktop support, internal APIs, and much more. That's the power of Oblien, and it's the vision we started working towards a year ago. We're still building on it. If you need battle-tested sandboxes, persistent workspaces for your AI agents, or environments to run your apps, Oblien is the way.
3
3
1
13
2,051
Oblien retweeted
We previously added MCP to OpenShip so you could control the platform from your coding agents. But we started thinking: why should you have to leave OpenShip and go through all those connection steps just to use your own agents? What if you could use your existing coding agent directly inside the OpenShip UI? You could also let it work automatically based on triggers. For example, get a report when a service goes down or a deployment fails, and let your agent investigate what happened -> then send you message via your notification channel. That's what we're working on: bringing your existing coding agents directly into OpenShip Desktop. For example, if a deployment fails, your agent can investigate the issue and you can apply its fix with one click, without leaving OpenShip.
10
4
1
81
4,325