Oxide

Register an API. Get a product.

Oxide reads an OpenAPI document, mounts the service behind one door, and lets you compose what it returns into pages — written as definitions, edited in the browser, served with no build step in between.

One door

Every service registered here — your own, a provider's, a bank's — answers at one address, under one sign-in, with one table that decides who may see what. The provider authenticates you; Oxide decides what you are allowed to reach.

Pages made of data

A view names the fragments it needs and the shape it wants them in. A fragment names its sources. Nothing hand-wires a request to a table, so the same data can be read three ways without being fetched three times.

Content and interface, both

Articles are content. So are the definitions that draw these screens: they ship as files, are read into the content core on install, and can be edited — or reset to what shipped — from the admin.

This page is one of them. Editing it is a content edit, not a deploy.