Shane

Im tired of infinite canvas startups. Im tired of generative video snake oil providers. Im tired of hype for hyperframes, as html and playwright is a dumb long term solution for video rendering. So I decided to build Raea. Open source. Free for everyone. Faster and more capable than hyperframes or remotion. (10-20x faster with real footage and complex scenes). And it renders without a browser…. Capable of more than just video. It’s built on @BevyEngine so it’s highly capable at producing 3D art, shaders and games. It’s also built on Blitz Dom @dioxuslabs , and a bridge between the page and the 3d world behind it allows you and your agent to write everything in typescript and react… without a browser. This video below was made entirely with Claude, Raea, and a weekend. I never had more fun playing and toying with creative work than I did making this. But to be honest, that’s not where I’m stopping. I want Raea to be an engine that correctly empowers creatives and agents, while not cognitively offloading the parts that make your work unique. I’m excited to continue working on this project as long as I can, and always open to feedback!

Thanks to everyone who filed issues and sent PRs this round: JimGHTB12, Ragulsundaram, SirSicard, Jameschuthink, Zeken0, TRDEFI, JoacoRea, juansilvadesign, Omkar-Hundre, ahmedNY and jbilakhi. Get the app for Mac, Windows or Linux: raea.io The code: github.com/shinyobjectz/raea

raea is built for AI agents. Tell yours what you want to see, and it writes the scene and renders it. The raea skill teaches your agent the things only raea can do. Grab it and open to contribute! github.com/shinyobjectz/raea…

Every render now says what it found, and keeps it. A part clipping into another fails the render, however its output is piped. `raea findings` sets each render against the one before: what’s new, what’s still there, what you fixed. Your agent can’t quietly skip it.

Same code, same pixels. Every time. We hunted down every bit of randomness, right down to the sparks in a particle fountain. Render something twice and you get the same frames twice.

Music can be code in raea too. Tone.js runs inside the engine with Firewheel, this way a score is just TypeScript. Play real instruments from open sample libraries, describe one in words and TokenSynth makes it on your machine, read and write .mid. Build your own instruments.

We cut a music video to a hyperpop track without touching a timeline. 'raea song' heard it: 185.9 BPM, the build, 3 drops, 3 stops, 10 hits, and every cut lands on them. On the first drop 546 cubes get smashed with real rigid-body physics. Music driven video is ez-pzy.

Blender and Godot, scripted from TypeScript. raea/blender types @Blender whole Python API. raea/godot types every @godotengine class and runs on GodotJS. With `raea blender run` and `raea godot run`, either engine is one more step in a raea workflow. Each half of this video was drawn by its own engine, from one shared timeline.

Want to edit the thing yourself? Raea exports projects to @capcutapp projects and can render transparent video files for overlays. Raea does the dirty work so you can do the real magic.

Bevy has a huge plugin ecosystem, and now you can use it from TypeScript. 77 crates come built in: avian and rapier physics, hanabi GPU particles, 3D text, tilemaps, networking. Each one is a typed import. Any other Bevy plugin, you declare and raea generates its bindings.

We rebuilt 143 of Bevy’s own examples in raea, and checked every one against Bevy’s picture, frame by frame. Bloom, fog, area lights, PBR, glTF, compute shaders. If Bevy can draw it, you can now write it in TypeScript.

DLSS this. DLSS that. DLSS on MacOS? Yes. Raea supports DLSS even on Mac with MLX. Oh, did I mention we support ONNX, MLX, and CoreML? raea neural mlxdlss runs it on any render. Bring your own MLX-DLSS build and weights.

One render, and it looks like a tape you found in a drawer. Ray-traced light, water, fire and physics, then a whole VHS deck on top: tracking errors, a photocopy negative, color that smears on the kick, the VCR's own clock in the corner. Visual effects, color grading and finishing are just another typescript file.

You (or your agent) can write your own GPU shaders in TypeScript now: post effects, compute shaders that build meshes, your own draw calls. This is the Game of Life running entirely on the GPU. We seeded it with our cat. It went through all nine lives in under two seconds.

Heard of @anomalyco's rune? Write an app once in TSX and it runs as a native window and on the web. You can also drop Rune layers into any page raea renders, and they’re drawn straight on the GPU.

Your three.js text effects come along too. These are lettra’s own docs figures (@joyco_studio text for three.js) rebuilt in raea. Its TSL shaders compile to WGSL through three’s own node builder: the same shaders you’d run in the browser.

If you’ve built something in React Three Fiber, you can now render it straight to video. No browser, no screen recording, every frame exact. It works the other way too: a raea scene can drop into three.js on the web.

HTML and CSS render a lot closer to Chrome now. Gradient text, SVG that draws itself, cards that flip in 3D. Name any Google font and it loads; give a video a URL and it plays. The devil is in the details, but damn it feels good to render animations at lightspeed.

Any Android game, taken apart for ads. `raea decompose` opens a game's APK and takes out its own characters, weapons, upgrades and props as models, sorted by kind. One game gave us 1,144 assets. We capture real play, frame-exact, and cut the ad from both. Unity and Godot games today.

Want to run raea in the cloud? Now with linux support and a docker image, you can deploy to the sandbox of your choice.

Fun fact: the entire desktop app was also built entirely in Raea's engine. That same ui kit for react is fulty transformable and usable in any 3d world. Buttons, sliders, menus, text boxes, and it renders anywhere raea does.