The core language shipping now
The major language features are implemented and shipping. Value types for games and money, capability-secured I/O, partitions you can snapshot and migrate with a memory copy, actors, a JIT on both ARM64 and x86-64, session hibernation, and the tooling around it all: a language server, a debugger, and the in-browser playground. The 0.x releases on the news page track this work, and it continues through everything below.
Evaluation with testers in progress
SCUA is in private evaluation. Invited testers get the prebuilt toolchain, the full manual, and a direct line to us, and what they hit steers the work. This is deliberately a small circle: the fastest way to make the language good is a handful of people building real things and telling us where it fights them. If that could be you, get in touch.
The package manager built, launch ahead
scua-pkg is verb-complete today: publish, resolve, vendor, verify, and the trust machinery, exercised against directory registries, which the design makes most of the product. The launch step is the public registry: a static, CDN-served index and a signed transparency log that exists from the first public publish, because first-seen history cannot be retrofitted later.
Public availability ahead
Downloads for everyone, the public registry live, and documentation that stands on its own. The gate is what evaluation tells us, never a date: the language goes public when testers stop finding the sharp edges before we do.
Full open-source release ahead
The language, the runtime, and the tooling open up. A scripting language earns trust by being inspectable, and we want SCUA to outlive any one company's roadmap. Open source is how both of those happen.
Running alongside
Three tracks that cut across every step above rather than slotting between them.
Reach. SCUA runs natively on macOS and Linux, and anywhere WebAssembly does. Windows is next, then iOS and Android, then the consoles. On platforms that forbid runtime code generation the interpreter is the runtime, which is why we keep making it faster in its own right.
Performance. The interpreter passed Lua's and the JIT trades wins with LuaJIT on our suite; the remaining gaps, deep recursion and string-heavy code, are known work. Further out we intend to explore ahead-of-time compilation for the platforms that forbid JITs.
The agent runtime. Hibernation was the first piece of a session runtime for AI agents: sessions that cost nothing while idle and wake exactly where they left off. Snapshot, fork, and replay for agent sessions are designed and queued behind it.