Your mission control for software projects and software engineering agents. Keep momentum on any device with sandboxed dev environments in our cloud or your VPC.
This is the 5th launch from Ona . View more
Ona (formerly Gitpod)
Your personal team of software engineering agents, sandboxed in ephemeral environments with editing via embedded VS Code and support for desktop IDEs. Collaborate on any device from phone to tablet or laptop.
Free Options
Launch Team
Ona
Hey PH! Lou from Ona 👋
Ona (formerly Gitpod) was started over 5 years ago to bring one-click development environments that beam developers into a ready-to-code environment. Now, as Ona we use that same foundation to bring about the future of developer tools that goes ‘beyond your ide’.
We call Ona ‘mission control’ as it’s like having a personal team of software engineering agents running in their own isolated development environments. You get to fire off as many tasks as you need in parallel and easily switch between them.
What makes Ona work:
- Sandboxing: Each agent gets its own throwaway, fully configured environment
- Parallel: Fire off multiple agents in parallel and in the background
- Handoff: Jump into VS Code browser to review or open your desktop IDE
- Mobile: Launch work from your phone and finish on desktop
Last week, Ona co-authored 60% of our own PRs and co-authored 72% of lines of code. Ona is usable not just on the weekends, but also at work. Ona is deployed in the Fortune 500 with support for private LLMs, all deployed in your VPC.
You can try Ona for free at ona.com.
You’ll also get $100 in credits if you upgrade to Core tier in September.
Would love to hear what you think of what we've built!
This space is heating up with recent news from Devin, and now Ona.
Ona
@michael_aring - It is ! We're certainly not alone in recognizing how agents are fundamentally changing software and how our tools now need to adapt.
On this topic, a couple of ways that Ona is different to Devin (for enterprises, that is) is that with Ona you can bring your own API keys (AWS Bedrock, private models, etc) and everything runs in the enterprises VPC so no code, prompts, customer data etc leave their infrastructure. Plus, Ona is built on a CDE foundation so you get dev container integrations, editors etc all battle tested over many years.
Both humans and agents working in the same secure and standardized development environments.
Ona
Hey Product Hunt 👋
Johannes here - Co-founder and CEO at Ona. After years of Gitpod, we're excited to launch Ona! Give it try and share with us what you think!
I had a great conversation at LatentSpace with @swyx and @csweichel about the launch
Ona
@johannes_landgraf - ton of great context in there !
Triforce Todos
Feels like carrying a whole dev team in your pocket, agents you can spin up anytime, anywhere, and know things won’t get messy.
Ona
@abdul_rehman - the 'won't get messy' part is really important.
At many of our customers developers either weren't allowed or were afraid to let agents tools touch their codebase because of data privacy concerns or the risk of breaking their local environment.
If you're running agents directly on your laptop, you're always inches away from corrupting your entire file system, accidentally exposing secrets, or having multiple agents interfere with each other.
Ona environments are ephemeral so each agent get a fresh, fully-configured environment that is destroyed after the task so you can be more experimental and delegate bigger, riskier tasks to the agents.
GraphBit
My IDE just got a whole co-pilot squad. Curious, what’s been the most surprising task teams let Ona agents handle?
Ona
@musa_molla great question! 'Most' surprising is hard but a notable one: a large customer of ours (major financial institution) was getting DDoS'd and needed to apply an emergency firewall change. One of the team on a Zoom with other engineers, pasted the error into Ona, and watched it find a solution, apply Terraform changes, and deploy the fix, all from inside their internal network while under active attack.
Everyone on the call requested access to Ona afterwards!
spring.new
Really like how you’ve framed Ona as “mission control.” The ability to spin up parallel sandboxed agents and jump into them from anywhere feels like it could replace a lot of dev context-switch pain.