The API reference of our Ruby gems, built from the source with RDoc on every release tag and published here at /rdoc/.
A store and distribution platform built on WarpEngine: catalog, purchases, entitlements and gated downloads, with the desktop client as its front end.
Our store for Batocera: pulls Teletype Games releases straight onto a retro box, under its own EmulationStation menu entry, with metadata and box art.
Our store for RetroArch: the Teletype Games catalog as two playlists with box art, on any machine RetroArch runs on.
WARP64U, the Teletype Games store on the C64: lists the C64 shelf over plain HTTP, installs and updates titles on a disk drive, and starts them.
Turn any Rails app into a retro game catalog: push a game, the CI builds it, the catalog publishes it, and every store client can install it.
Since WarpEngine 1.0: what the admin does, as a JSON API under /api/admin/v1, with a live OpenAPI 3.1 document and an MCP server.
The reusable Batocera store engine: any WarpEngine-based site can ship its catalog to a retro box with a config file and a three-line installer.
The file area of Teletype Games on a telnet line: the C64 and Plus/4 shelves, downloaded by ZMODEM or XMODEM
The WarpEngine Client app: the catalog as a grid of cards, the store engine built in, and a settings dialog for the stores on the machine.
The RetroArch store engine: any WarpEngine catalog becomes .lpl playlists with box art, on desktop, Android, the Steam Deck or a handheld.
Everything a small game studio needs, on its own server in minutes: a catalog, a Git forge and CI, a VS Code toolbox, and stores for every screen.
The VS Code extension for WarpEngine games: a new game from the host's template, metadata checked against the host, play in the web runtime, connect, release and the catalog, without leaving the editor.
Everything about WarpEngine in detail: platforms, endpoints, access, the image library, Woodpecker pipelines, outlets, shelves, installation and admin integration.
The shared core of our store engines: one file that knows the WarpEngine catalog, so an engine only has to know its host platform.
WarpEngine Catalog Protocol: the endpoints a WarpEngine server offers to catalog readers, each with its response shape.