Pictures, made locally
Describe it. It paints it.
You write a description; easel produces a finished picture file, full-size, in whatever art style you name. It runs on hardware in the house — no part of a render is sent to a cloud service. It draws RealKeep's world art and the seventy-picture design gallery.
Real output
Eight styles, one pipeline.
Name a style and easel renders in it — not a filter dropped over a photo, a picture built from your words. The eight below are real output, one per style, one pipeline. Tap any one for a larger copy.
every picture on this page came out of the pipeline this page describes — tap any tile for a larger copy
One render, start to finish
Every render carries its recipe
Tools that show their work — here the work rides inside the file. Every full-size render easel makes carries the recipe that made it. The previews on this page are compressed copies — too small to hold one; the full files do: the full render graph, each step and setting in the order it ran, written into the file's own metadata. Anyone holding one can read how it was produced. All seventy gallery renders carry it.
The recipes go deeper than the gallery: the whole diffusion pipeline was chosen on a public bench — painter head-to-heads, step ladders, resolution ladders, cold-start costs — run on real product content with the receipts attached, wins and losses both. Read the diffusion research →
Where it shows up
One pipeline, two places it shows up.
RealKeep's worlds aren't stock art. Each scene is rendered from a description the moment the story needs one, and the design gallery is seventy finished renders off the same pipeline.
a RealKeep scene, from the description beside it
the scene prompt
a detailed 16-bit pixel-art scene of a warm seaside town at dusk, glowing lantern windows, cobbled street, small boats in a bay, crisp clean pixels, retro SNES JRPG aesthetic, rich sunset palette
a scene the story needs → keel → easel → the world you see
See RealKeep →