Sandboxed by construction
Every applet runs in an iframe with an opaque origin. It never holds a credential, calls an API or
touches a database. It asks the Rack over postMessage, and the Rack decides, enforces and
persists.
Documentation · ziprack/1
Meet zipRACK.
zipRACK is an open standard for interactive web experiences. You build an applet:
a small static web app, shipped as one zip, that declares what it needs. Any Rack,
which is any host that implements ziprack/1, runs it unchanged. The Rack signs people
in, keeps their work, calls the models, holds the room together and reports on all of it. Your
applet owns everything the participant sees.
@ziprack/sdk. You can build and test the whole thing locally in mock mode.
Applet Packages
I’m ready to ship
Start with Review & Release
Upload your zip, see what happens when a new version asks for more than the last
one did, and learn how promotion and pinning affect the people already using your applet.
Review & Release
Why zipRACK?
There are plenty of ways to put an interactive experience in front of people. We think zipRACK is the best way to build one that is safe to run, easy to review and still entirely yours to design.
Declared, not integrated
The manifest names every capability an applet will call, and nothing in the package holds an endpoint, a key or a credential. The Rack refuses anything undeclared. When a new version asks for more, it waits for a human to approve it.
Built once, run on any Rack
Capabilities are versioned contracts that change only when what your applet sees changes. An applet
built against db@1 runs on every Rack that implements it.
Explore the documentation
Prologue
Start here. Learn how your applet and the Rack divide the work, and how versions affect the people using your applet.
Building an Applet
Everything you need to package an applet, declare what it needs, and talk to the Rack from your own code.
Capabilities
Each capability is a contract your applet declares in its manifest. Ask for exactly what you need, and the Rack takes care of the rest.
Shipping
The environment your applet runs in, and what happens between uploading a version and your participants seeing it.
Resources
Condensed references you can drop straight into an applet project.