Alloy

Alloy is not another wireframing tool. It's a bet that the fastest way to explore a product idea is to start from the product itself—the actual codebase, the real components, the live pages—and let anyone on the team, not just engineers, drive the changes. The tagline says it plainly: "Codebase Sessions for Everyone, Not Just Engineers." That's a deliberate provocation to a developer-tools industry that has long assumed the terminal is a membership card.

The browser is the new whiteboard

For years, product ideation has been stuck in a loop: a designer sketches in Figma, a PM writes a spec, an engineer interprets both, and somewhere in that game of telephone the original idea loses its shape. Alloy's answer is to collapse that loop by making the browser the canvas. Instead of importing screenshots or rebuilding screens in a design tool, you capture your live product—either by connecting your codebase or using a browser extension—and then prompt changes in plain language. The result is a prototype that looks like your product because it is your product, rendered with your real components and design system.

The homepage demonstrates this with a fictional freight dashboard: a user asks for a new "Shipments" tab, and within minutes a teammate is reacting with "you made that in 5 minutes?!" That's the emotional core of the pitch—speed, but more importantly, fidelity. Alloy's FAQ makes the point explicit: "Everything you build automatically looks like something your designer made." That's a claim no generic app-builder can make, because generic builders don't know your design system.

From screenshot to sandbox: how Alloy captures your real product

Alloy offers two on-ramps, and the distinction matters. The browser extension requires no setup—it captures your product instantly, letting you start prototyping right away. That's the low-friction path for a PM who wants to tweak a page without waiting for an engineer. The more powerful path is connecting your codebase, which requires admin permissions and about 15 minutes of setup. Once connected, Alloy runs your entire app in a sandbox, giving the agent full context: your components, your pages, your themes.

The difference is profound. A screenshot-based tool can only guess at your design language; Alloy's codebase connection means the agent is working with the same source of truth as your engineers. When you prompt for a change, it writes production code, not a throwaway mock. That's why Alloy can push to a Pull Request at any time—the prototype isn't a separate artifact, it's a branch of your actual product.

Cloud agents vs. the local dev environment

The FAQ draws a direct line to Claude Code: "Alloy lets anyone in your company start a session from the cloud, without having to run a developer environment on their local machine." That's the core architectural bet. Local development is a barrier—it requires setup, dependencies, and a certain level of comfort with the command line. Alloy's cloud agents run in a sandbox, so a designer or PM can start a session from Slack, run multiple sessions in parallel, and share them with a link. No local environment wrangling.

This is a meaningful shift in who gets to touch code. Alloy isn't replacing engineers; it's removing the gatekeeping that kept non-engineers from prototyping with real code. The company's library includes a post titled "Cloud Agents vs. Local Development: Why Product Teams Are Moving to the Browser," which frames this as a broader industry trend. For Alloy, the browser is not just a convenience—it's the platform that makes "codebase sessions for everyone" possible.

The browser extension as the zero-setup on-ramp

The browser extension is a clever piece of positioning. It lowers the barrier to entry to zero: install, capture, prompt. No admin permissions, no 15-minute setup, no IT approval. That's the hook for a PM who wants to test an idea today. The extension is also a Trojan horse—once you've seen how easy it is to prototype with your real product, you're more likely to ask for the full codebase connection, which unlocks the production-code pipeline.

The extension also solves a practical problem: many products are not easily runnable in a local environment, or the codebase is too large to clone. Capturing the live product from the browser is a pragmatic workaround that still gives the agent visual context. It's not as deep as a codebase connection, but it's enough for visual prototyping, and it's a smart on-ramp for teams that aren't ready to commit to a full integration.

Naming tells the story: Alloy's alloy of design and code

The name "Alloy" is a metaphor that works on two levels. Metallurgically, an alloy is a blend of metals that's stronger than its components—here, the blend is design and code, or more precisely, the product team and the codebase. The name suggests a fusion, not a separation, which aligns with the product's goal of breaking down the designer-developer handoff. It also avoids the common "AI" suffix or the generic "Builder" label, positioning Alloy as something more subtle and more integrated.

The domain, alloy.app, is clean and memorable, and the brand identity—with its simple wordmark and playful emoji reactions in the demo—leans into approachability. This is not a tool for the terminal; it's a tool for the whole team. The naming reinforces that: "Alloy" is short, friendly, and suggests a material that's both strong and flexible. It's a name that works for a company that wants to be the default prototyping layer for product teams, not just another developer utility.

What Alloy doesn't do yet—and why that matters

Alloy is transparent about its gaps. There's no Figma import yet, though the FAQ says it's on the roadmap. The team recommends capturing your actual web app rather than importing from Figma, which is a telling prioritization: real product beats design mock. You can export to Figma, but the flow is one-way. That's a deliberate choice to keep the focus on the live product.

The lack of Figma import is also a signal of Alloy's thesis: the design tool is not the source of truth; the codebase is. That's a controversial stance in a design-tools industry that has long treated Figma as the center of the universe. But Alloy's bet is that as AI makes code generation easier, the real product becomes the most accurate representation of intent. The company's library includes posts like "What Is Vibe Designing? Defining the New Category Alloy Is Pioneering," suggesting they're consciously trying to create a new category that bridges vibe coding and design.

For product teams, the open questions are practical: How well does the agent handle complex, enterprise-scale codebases? The security page promises enterprise readiness, but the proof will be in the pull requests. And for non-engineers, the learning curve is not in the tool but in trusting an AI agent to write production code. Alloy's answer is to make the process collaborative—share a link, get comments, push to GitHub—so that the human stays in the loop. That's a sensible middle ground, and it's why Alloy feels less like a toy and more like a genuine shift in how product teams prototype.

If you're a PM who's tired of waiting for engineering capacity, or a designer who wants to see your ideas in the real product, Alloy is worth a look. It's not a replacement for your design tools or your engineers, but it might just be the bridge between them.