From intent to application.

Define the solution.

Describe what your app should do: its data, pages and rules. These definitions are the contract. MatterData runs it as a working application.

See the contract

The what, in a few lines.

Members have names and unique email addresses. The board gets a searchable list with CSV export. You declare these requirements; the shared runtime handles the database, interface and access checks.

schema.edg · Example

table members "Members" {
  first_name text required "First name"
  last_name  text required "Last name"
  email      email unique  "Email"
  joined_on  date          "Joined on"
}

pages/members.edg · Example

page members "Members" {
  route: /members
  access: board

  report of members {
    columns: first_name, last_name, email
    search: first_name, last_name
    sort: last_name
    export: csv
  }
}

Focus on the outcome.

Manage members, collect signups, organise work. Put the decisions that matter to your organisation into a definition you can read and review.

Create with AI.

Write the contract yourself or ask AI to draft it. A compact format keeps it reviewable, and the compiler checks definitions before they run.

Build on a shared runtime.

Your contract describes what should happen. MatterData owns how it happens. Improvements to the runtime benefit every app.