Identity is the hard part
A character has to look like the same person across hundreds of images and dozens of sessions. One good frame proves nothing; the tenth frame, in a new outfit, does.
Investors
The art pipeline for story games, built in production.
Sprite Studio is the tool an independent studio built to produce its own visual novel, now becoming a product. This page covers what exists today, why the approach holds up, and where it is headed.
The problem
Making game art is a pipeline problem, not a prompt problem.
Producing art for a narrative game is a last-mile problem. A chapter needs hundreds of images that must read as one coherent world: the same faces, the same clothes, the same light, frame after frame.
Generic tooling solves the single image and ignores the pipeline around it. Identity, consistency, naming and export are left to the person doing the work, and that is where the hours and the drift live.
The last mile is manual
Cut-outs, cropping, naming, export folders, idle and hover pairs. The work no model does for you is the work that quietly eats the schedule.
Consistency drifts across sessions
Without a shared identity and a shared library, every session slowly reinvents a slightly different game. The art stops matching the story.
What exists today
The whole pipeline runs, screen by screen.
Depth, not demos: every number below is shipped in a private preview and exercised by a production in active development.
16purpose-built screens, from characters to animation
75scene positions, each with its own concept LoRA
38hand-made sprite poses
72tools exposed to Claude over MCP
163backend tests plus a pixel golden test
Why local-first
How the architecture works
The app runs on the creator's machine, not on ours.
Creators already pay for their own models, and game art is sensitive work. Sprite Studio runs on Windows on top of a local ComfyUI engine, so the engine and the library stay on the machine doing the work.
Cloud image models are reached with the creator's own keys through OpenRouter and fal.ai, and heavy video can run on a GPU the user controls. There is no cloud account to create, no lock-in, and nothing to migrate when someone leaves.
Why it holds up
Depth built from daily production use.
The defensibility is in the accumulated, unglamorous domain work, not in a claim about rivals.
A domain library, not a wrapper
Seventy-five researched scene positions each carry their own concept LoRA, and shared presets keep a whole project on one consistent line instead of drifting screen to screen.
Production-hardened depth
Sixteen purpose-built screens replace the node graph, with export formats and naming baked in. A suite of 163 backend tests plus a pixel golden test keeps it stable as it grows.
A working automation surface
Seventy-two MCP tools let an agent drive every screen under a spend limit, which is the groundwork for studio-scale, repeatable workflows.
Traction
Traction, stated plainly.
There is real usage and there is an honest absence of the numbers some decks lead with. Both are below.
- A private preview running the v1.6 series of releases.
- A changelog of shipped releases, from the current series back.
- Used daily to produce Valley Awakening, the visual novel in active development it was built for. The dated development log is public.
- A disciplined test suite: 163 backend tests plus a pixel golden test that must pass before a release.
No public user numbers exist yet. When they do, they will be stated with dates.
Direction
Where this goes next.
Plans, not commitments. Each item is labelled with its real status.
Train identity LoRAs in-app
Pick approved images, auto-caption them and train an identity LoRA on the creator's own GPU, then attach it to the character automatically. Cleaner video loops with longer crossfades and frame trimming are next as well.
Next
Generalise to more pipelines
As the model improves, the same screens map onto 2D game pipelines and 2.5D scene tooling beyond the visual novel this started as.
Exploring
The commercial model
How Sprite Studio will be sold is not public yet. No pricing or tiers are set; early-access conversations will shape them.
Not public yet
Context
Team, market and first buyers.
Stated honestly — what is public, and what belongs in a conversation.
A small independent studio
Sprite Studio is built inside Wargnema, the studio behind Valley Awakening. Team backgrounds and roles are shared in investor conversations.
Built where its first buyers are
The pipeline grew up in solo and small-team narrative game development — the segment it serves first. Market sizing belongs in the conversation, not on this page.
Community-first, starting with early access
Early access comes first, then the developer communities this pipeline was born in. The exact sequence is still being shaped.
Contact
How to engage.
Technical and product walkthroughs are available in a call, and the private preview can be demonstrated live. If you run an accelerator programme or a fund, say so in your note — we are open to the right next-stage partner.
Planning an intro
Include a few lines so the first call is useful:
- Who you are and the fund or programme you represent.
- What you would like to see: the product, the technical architecture, or both.
- Any timeline you are working to.
This page is provided for information only. Nothing on it is an offer to sell or a solicitation of an offer to buy any security, and no statement here should be relied upon for investment purposes. Forward-looking statements describe plans, not commitments.
Early access
Built in production. Opening to outside studios.
Request access, or read the roadmap to see what ships next and what is still being explored.
- Engine
- ComfyUI · local
- Models
- OpenRouter · fal.ai
- Output
- Ren'Py-ready PNG / WebP
- Status
- Private preview · 18+ capable