FOR ENGINEERING LEADS AND SECURITY

Check everything before you commit.

SDK and examples MIT licensed. Every dependency and every unsafe block is listed in our public records. Before 1.0, names can change.

One dashboard, dark and lightDrawn by Aster

The details your review will ask for

The plan for 1.0

From 1.0, breaking changes come only in major releases, with at least one release of warning. Until then, fixes go into the next release.

We are aiming for 1.0 in early 2027.

This policy takes effect at 1.0.

How it is made

Most of Aster's code is written by AI coding agents under the direction of the company's human developer, who sets the goals, specifications and acceptance tests.

Licence and the EU Cyber Resilience Act

Licence and notices

SDK and examples MIT, runtime under the Aster Runtime EULA, published by Barnyard Greens LLC, with every third-party licence listed.

Example evaluations (illustrative)

Read 3 short examples

The security review

A reviewer downloads the parts list, re-runs the licence and vulnerability checks, and reads the unsafe-code list. Each number here says how it was counted.

The licence sign-off

Legal finds the SDK and examples under MIT, the runtime under a named EULA, a named publisher and a complete list of third-party licences.

A first prototype

An engineering lead builds one screen against the C interface and runs it on Linux and in a desktop browser.

Good to know

  • Aster is before 1.0, so names can change.
  • Support is free for now; there are no paid plans. Security reports get a reply within 5 business days.
3 more to know
  • Releases aren't signed. The signing tools are ready; the release key comes first.
  • There's no Mac or iPhone version.
  • On the web there's no touch, pinch or input-method typing, and no direct screen-reader bridge on desktop.