Sparkles Wants Your Whole Team to Ship Code - Without Ever Opening a Terminal
The YC W26 startup lets marketers, designers and operators change a company's real codebase from a browser. An AI agent does the work in a sandbox, and an engineer still gets the final say.
There is a moment familiar to almost every software company. A designer spots a typo on the pricing page, or wants a button nudged two shades bluer. It is a five-second fix. And then it isn't - it becomes a Slack message, a ticket, a place in the engineering queue, and three days later the typo is still there. The person who wanted the change and the person allowed to make it were never the same person.
Sparkles, a company in Y Combinator's Winter 2026 batch, is built around closing that specific gap. Its pitch is short: let anyone on the team make the change themselves, and let an engineer approve it. The tagline on its site is blunter still - "make everyone on your team an engineer."
The way it works is deliberately unglamorous. Someone technical connects a company's existing GitHub repository to Sparkles once, sets up environment variables, and defines who is allowed in. After that, anyone with a company email address can log in through a browser, describe the change they want in plain language, watch a live preview, and hit upload. An AI agent implements the change inside an isolated sandbox running on the real codebase, and the result comes back as a pull request - the same review-and-merge step engineers already use every day.
01 / The ProblemThe learning curve was the product
Tools that write code with AI have multiplied over the last two years. Most of them assume you are, on some level, a developer. They ask you to clone a repository, run a command in a terminal, start a dev server, resolve a merge conflict. For a marketer or an operations lead, each of those steps is a small wall. Stacked together, they are a reason to just message an engineer instead.
Sparkles treats that friction as the thing to remove. There is no command line, no local environment to install, no Git vocabulary to learn. The company describes its platform as one that "fully abstracts from local development" so that go-to-market, design and marketing teams never have to know what a CLI is. What is left is a chat box, a live preview, and an upload button.
02 / How It WorksDescribe it, preview it, upload it
The mechanics matter here, because the safety of the whole idea rests on them. Sparkles does not hand non-engineers write access to production. It gives them a way to propose, and it gives engineers a way to say no.
The pull request is the quiet star of the product. It was invented decades ago as a way for engineers to review each other's work before it ships. Sparkles repurposes it as the guardrail for people who have never written code at all. Nothing lands without a human looking at it first. That is a design choice, not an afterthought - the platform adds enterprise rulesets for managing pull requests, batching commits to reduce review load, and controlling access by email domain.
03 / The DifferenceBuilt for the codebase you already have
The obvious comparison is Lovable, and Sparkles invites it - one of its own descriptions is "Lovable, but for your existing projects." That last phrase is the whole argument. Tools like Lovable, Bolt and v0 are dazzling at building something from nothing: you type a prompt and a fresh app appears. But most of the work inside a real company is not greenfield. It lives in a messy, revenue-generating repository that nobody wants to break.
Working on existing repositories is harder, and it is also where the money is. It means respecting real branches, real environment variables and real review processes. Sparkles' bet is that the tool which wins non-engineering users will not be the one that generates the most code, but the one that decides, most carefully, who is allowed to press merge.
04 / The FounderA 20-year-old with a specific grudge
Sparkles is led by Ai Daniil Bekirov, who goes by Dan. He is 20, Ukrainian, and dropped out of University College London. Before starting the company he was a Cursor ambassador, shipped for Structured (a YC F25 company), and interned at Iterate, where he worked alongside the former CTO of Monzo. He has also made a handful of small angel investments in other early-stage startups.
His thesis is not that engineers disappear. It is closer to the opposite: engineers should stop being a help desk for one-line changes. Every hour a senior developer spends nudging a button two shades bluer is an hour not spent on the work only they can do. Sparkles is an attempt to hand those hours back, without handing over the keys.
05 / The BackingWho is betting, and why it's interesting
Sparkles is backed by Y Combinator and Moonfire Ventures, with angel investment reported from people at OpenAI, Anthropic, a16z, General Catalyst and Cloudflare, and a seed round reported at roughly $3.5 million. Early users listed on its site include Turing, Pax Historia, Fondo and Revnu.
The cap table is worth a second look, not for the names but for what they imply. Some of the same people building the underlying models are funding a tool whose entire purpose is to decide who gets to use them safely. It is a small signal about where AI coding may be heading: away from raw generation, and toward governance - permission with a review step attached.
Find Sparkles
Note: funding figures and investor names are drawn from public reports and the company's own materials, and are approximate. YC's demo and founder interviews are shared on the founder's X and LinkedIn accounts above.