We're glad you're here.

This is a Notion for the Warpforge and Warpsys projects.

The pitch in short: We’re offering software build tools for language-agnostic, hermetic builds, for developer productivity, security, and sanity. It’s tooling for developers. It’s open source. It gives reproducible environments, so you can do reproducible work. And we hope it’ll take over the world.

warpforge is a build tool. Or more precisely, a build framer tool: it sets up environments, runs whatever you want in it (can be other build tools; make, rake, javac, go, npm, etc, etc), and helps you manage the outputs. It makes things reliable and it makes them consistent.

warpsys is a package ecosystem of stuff that’s easy to use in warpforge, so that when you want to get stuff done, you can build upon what others have already made!

But it's optional; you can use warpforge however you want, with whatever software inside it you like.

Packages in warpsys are packaged as Zapps to make them zero-dependency and path-agnostic. More information on Zapps is available at https://zapps.app.

We’re building everything with hashes for the inputs, hashes for the outputs, and hashing the instructions too — so, perfect caching! and, solid supply chain security!

Examples!

Real runnable examples speak a thousand times better than marketing text, so, here we go, let's jump straight into it, with real stuff:

Check out this link:

http://catalog.warpsys.org/warpsys.org/bash/_replays/zM5K3Vgei44et6RzTA785sEZGwuFV75vCazjhR11RH5veFdMTx7F5cg2c4NA5HXPK8Zv5TQ.html

That JSON you see there is a real-world example of how we built something in warpforge: in this case, it’s bash!

• You can see all the inputs enumerated. You can see exactly the instructions we ran. And if you click the breadcrumbs at the top of the page to get back to the release info: there you can see the exact hash of the outputs we produced, too.
• And you can follow the links of each of the inputs to find the same info for them.
• You can do this recursively, to see where every single bit in the system came from.

That’s the pitch: in a system like this, there’s nothing you can’t understand, and nothing you can’t fix.

(Do you write a lot of JSON to do that? Yes. It’s very “API driven”. Don’t worry. We’re also building tools to give you higher-level authoring that’s more to-the-point. Or you can bring your own!)