exe.dev - Blurring the Lines Between Cloud Infrastructure and AI-Assisted Development

The developer landscape continues to evolve with new approaches that challenge traditional paradigms of cloud infrastructure management and software development. Among these emerging solutions, exe.dev has garnered attention for its unconventional approach that combines bare-metal virtual machine access with AI-powered coding assistance.

At its core, exe.dev offers a straightforward value proposition: users purchase a pool of CPU, RAM, and disk resources and can create as many virtual machines as they need. The experience feels refreshingly familiar—SSH in, and you're root with access to apt and systemd. This traditional approach contrasts sharply with the increasingly abstracted containerized serverless environments that have dominated cloud development in recent years.

What sets exe.dev apart is its integration of Shelley, a web-based AI coding assistant that operates within the development environment. The service emphasizes persistent, private-by-default servers with IAM-based sharing capabilities, creating a middle ground between fully managed cloud services and self-hosted infrastructure.

The community response to exe.dev reveals a polarized yet engaged user base. On one hand, prominent figures like Filippo Valsorda, known for cryptographic work and contributions to projects like Cloudflare's BoringSSL, have expressed enthusiasm: "I just vibecoded with exe.dev and Opus 4.5 a backoffice for our FIPS 140 validation... I have not looked at the code once. It works great." Similarly, developer Emmanuel Odeke notes that "exe.dev removes the laborious barrier between managing cloud infrastructure, building software, prototyping and ridiculously lowers the barrier to entry for me, I haven't enjoyed building software this much since perhaps discovering Go or self teaching C."

The sentiment extends to everyday developers who appreciate the practical benefits. As Mark Roddy shares, "Been using it for just over a week now. Really falling in love with it. Even with out AI coding features, I'm not sure how I'd do local development without it." The ability to "vibecode"—a term that suggests effortless, AI-assisted development—appears to be a significant draw for users.

However, not all reactions have been uniformly positive. One anonymous commenter on Hacker News dismissed the service with the blunt critique: "That must be worst website ever made." Such negative reactions highlight the challenges innovative services face when departing from established conventions.

The technical approach of exe.dev warrants closer examination. By providing traditional root access via SSH while layering AI assistance on top, the service occupies an interesting position in the development tool spectrum. This model challenges the notion that cloud infrastructure must either be fully abstracted (serverless) or require complex self-management. Instead, exe.dev offers a middle path that combines the control of traditional server management with the convenience of modern cloud services.

The persistence of virtual machines represents another distinctive aspect. In an era dominated by ephemeral containers and serverless functions that reset between executions, exe.dev's persistent servers offer continuity that some developers find essential for complex projects. As Stanislav Kozlovski notes, "The level of 'just works' polish that exe offers has astonished me... I find myself spinning up disposable VMs multiple times a day now."

The integration of Shelley, the AI coding assistant, deserves particular attention. User testimonials suggest it has differentiated itself from other AI coding tools. As XplsosivesX observes, "Shelley is seriously incredible, I use a lot of AI dev agents and y'all are really not talking about Shelley enough." This indicates that Shelley may offer unique capabilities or a superior user experience compared to alternatives like GitHub Copilot.

The service also appears to address the growing need for development environments that transcend traditional device boundaries. As one user expressed, "Seriously don't die. I haven't found a service I could code on my phone from like this. It's amazing. Now I'm programming remote servers. Stopped using copilot..." This highlights exe.dev's potential to enable development from virtually any device with an internet connection.

Despite these apparent strengths, questions remain about exe.dev's long-term viability and scalability. The model of providing persistent VMs with root access raises security considerations that may not be immediately apparent. Additionally, the economic sustainability of offering such resources—particularly when combined with AI assistance—remains to be seen as the service scales.

The emergence of exe.dev also prompts reflection on broader industry trends. As cloud providers increasingly abstract infrastructure away from developers, exe.dev moves in the opposite direction, bringing back the familiarity of server administration while adding modern AI capabilities. This tension between abstraction and control represents an interesting fault line in the evolution of developer tools.

The service's approach to team collaboration also warrants consideration. The mention of IAM-based sharing suggests an attempt to bridge the gap between personal development environments and team-based workflows. However, the practical implications of this approach in real-world team scenarios remain to be fully explored.

As the developer community continues to experiment with exe.dev, several questions emerge: Can this hybrid model of traditional server management with AI assistance compete with established cloud providers? Will the persistence of virtual machines prove to be an advantage or a limitation in an increasingly ephemeral computing landscape? And perhaps most importantly, how will the integration of AI tools like Shelley continue to reshape the fundamental nature of software development?

The early enthusiasm from users suggests exe.dev has tapped into a genuine need among developers for environments that combine control, convenience, and intelligent assistance. As the service evolves, it will be interesting to observe whether this initial momentum translates into sustainable growth and lasting impact on the developer ecosystem.

In a landscape dominated by incremental improvements to existing paradigms, exe.dev represents a more radical experiment—one that challenges developers to reconsider their relationship with both cloud infrastructure and AI-assisted development. Whether this experiment proves to be a passing curiosity or a harbinger of future approaches remains to be seen, but the conversation it has already sparked is undeniably valuable.