How it works

Three steps from an idea to something deployed

No scaffolding to wire together afterwards, and nothing generated that you cannot read.

Read the quickstart

  1. Describe the resource

    One definition names the fields and their types. It is the only place the shape of the thing is written down.

  2. Generate the stack

    The model, migration, service, handler, validation schema, typed client and admin screen all come from that definition.

  3. Deploy the binary

    One artifact carries the API, the admin panel and the assets. There is no runtime to install on the box.