Hoplite (YC S26) builds effortless cloud coding agents, and it isn't thinking small about scale.
"Our mission is to allow developers to deploy trillions of tokens a day, and see genuinely good output from it."
That's an infrastructure problem, and it's where Hoplite's engineering time belongs. Which is why the first thing a new user sees, an onboarding flow that feels personal from the very first screen, is not something cofounder and CEO Ryan Morrissey wanted to build from scratch.
How they found Context.dev
Hoplite and Context.dev are in the same Y Combinator batch, which is how Ryan and Yahia met.
"We were really impressed by all the capabilities of the platform and how they could improve Hoplite's user experience."
Fifteen minutes, end to end
The integration was a single afternoon task, and not a long one.
"Seamless set up, Yahia was immediately responsive and guided us through the installation. Took 15 minutes E2E, and we were pleasantly surprised at how easy it was to set up."
Emails in, brands out
The part Ryan expected to be painful turned out not to exist.
Hoplite already had one piece of information about every new user: the email address they signed up with. Turning that into a company identity is the kind of task that looks trivial until you start writing it, at which point it becomes a growing pile of regex, a list of free-mail domains to exclude, and a set of edge cases that never quite ends.
"The standout feature was the fact that we could pass the user's emails in directly, and Context.dev would automatically figure out what their domain was. I was worried about doing this manually and setting up all the regex, but Context.dev made it extremely easy."
Hoplite passes the signup email straight to the Brand API and gets back the company behind it: name, logo, colors, and the rest of the identity. No domain parsing, no exclusion lists, no maintenance.
Pricing you can forecast
For an infrastructure company watching its own unit economics closely, spend that can be traced and predicted matters as much as the feature itself.
"Pricing is also incredibly transparent and we can very easily track exactly what's being spent where, and forecast our exact credit needs."
The outcome
Hoplite's onboarding now recognizes the company a developer works at before they've typed anything beyond their email. Customers notice.
"Context.dev has greatly improved our onboarding experience, adding a real 'wow' factor that almost every one of our customers have commented on, asking 'How did you do that?!' It's a great way to make our platform feel more personalized."
Or, as Ryan put it more plainly: "They're always asking us how we do it haha."
Key benefits
- 15 minutes end to end: from first API call to a personalized onboarding flow in production.
- No domain parsing to maintain: emails go in, company identities come out, with none of the regex Ryan had budgeted for.
- Onboarding that gets commented on: nearly every Hoplite customer has asked how the flow works.
- Forecastable spend: transparent per-credit usage Hoplite can attribute and plan around.
Looking ahead
The onboarding flow was the first use, not the last.
"There's a lot more we have planned, for example simple features like automatically loading the logo of MCP servers that users add. The possibilities feel endless."
Want new users to feel recognized the moment they sign up? Context.dev turns an email address into a full company identity, including logos, colors, fonts, and context, through a single API call.