Launch HN: Hoplite (YC S26) – Effortlessly deploy cloud coding agents
Hoplite launches with a vision for the future of development, offering cloud coding agents that focus on reviewing product output rather than individual lines of code. This YC S26 startup addresses the challenges of scaling AI-powered development by providing isolated sandboxes and full dev environments. The discussion centers on its novel approach to cloud agents, technical implementation choices, and pricing compared to existing solutions.
The Lowdown
Hoplite is a new platform designed to effortlessly deploy cloud coding agents for software development. It aims to shift the developer's focus from reviewing code to verifying product output by automating tasks within real, isolated development environments. The founders, Bence and Ryan, pivoted from an AI investing idea to address what they saw as shortcomings in existing cloud agent solutions, believing that future development will involve managing hundreds of concurrent agents.
Key features and concepts include:
- Automated Workflows: Agents read code, edit, run tests, debug failures, and propose pull requests after sign-off.
- Four-Step Process: Connect a GitHub repo, describe a task, agents work in a real sandbox, and open a pull request.
- Real Dev Environments: Each agent operates in an isolated sandbox with a live URL, capable of booting the app, installing dependencies, running tests, and even driving a browser to check its own work.
- Concurrent Sandboxes: Each task (thread) gets its own machine, preventing slowdowns and allowing for high concurrency (up to 150 sandboxes per seat on Scale plan).
- Model Flexibility: Supports frontier models from Anthropic and OpenAI, with options for open-weight models and connecting personal API keys.
- Robust Infrastructure: Built on AWS, using Temporal for workflows, Modal for sandboxes (with potential future transition to AWS Lambda MicroVMs), and Planetscale for the database, emphasizing reliability and security.
- Pricing Model: Credits are prepaid and metered, with plans starting at $99/seat/month, setting sandbox capacity without upcharging on token or sandbox costs.
Hoplite's creators believe this approach reflects where mainstream development is headed, enabling developers to scale their efforts by reviewing product functionality rather than granular code changes. They are currently focusing on optimizing onboarding and preview experiences.
The Gossip
Cloud Critiques and Comparisons
Commenters explored Hoplite's distinction from existing tools like Cursor's cloud agents, Amp, GitHub Copilot Cloud, and Codex Cloud. The key differentiator for many was Hoplite's ability to boot an app on a live URL within its sandbox, enabling full PR testing without local checkouts. Discussions also touched on the pricing model, with Hoplite's higher base cost justified by not upcharging on token or sandbox usage, and offering features typically reserved for enterprise tiers.
Modal Musings and MicroVM Meanderings
The technical choices behind Hoplite's sandboxes sparked curiosity, particularly the decision to use Modal instead of solutions like Firecracker or other microVMs. The founder explained Modal's appeal (filesystem snapshots, programmatic build images) but also noted its autoscaling limitations and ongoing evaluation of AWS Lambda MicroVMs. The conversation included a brief mention of Daytona as a fallback, highlighting the complexities of building scalable cloud development environments.
Landing Page Levity and Legitimate Lessons
Several users provided feedback on Hoplite's landing page, with one commenter noting a 'generic Claude made animation' and 'AI slop' vibe. This critique led to an acknowledgement from the founder that a redesign was underway to present a more authentic and trustworthy image, suggesting a broader concern within the HN community about the perceived authenticity of new tech startups.
Nomenclature Nonsense and Netiquette Nuances
A minor but spirited debate emerged around a comment pointing out a naming conflict with `hoplite.gg`. While the founder dismissed it as unlikely to cause SEO issues, others debated the utility of such comments on HN. One user even cited HN guidelines against complaining about 'name collisions,' sparking a meta-discussion on appropriate comment etiquette and what constitutes 'interesting' feedback.