One engine, two ways in

The system that delivers releases and accounts for royalties on Aevora is open to you in two forms. Engine is the REST API, for teams that build their own product. Imprint is the finished platform under your brand, for teams that would rather not build one.

Engine
A REST API with a sandbox
Imprint
A platform under your name and domain
Add-ons
Stream Radar, Preflight QC, MCP server

Engine: build distribution into your own product

Engine exposes the catalog, delivery and royalty functions as REST endpoints. Your code creates releases, attaches audio and artwork, sends them to stores and reads the statements back. Your customers see your interface and nothing else.

  • Manage releases, tracks and artists from code
  • Start deliveries, updates and takedowns
  • Pull royalty and analytics data into your own dashboards
  • Test in a sandbox before anything reaches a store

Aevora Records

Sample data

Test modeKeys for the sandbox only.

  • Server key

    Read and write
    lz_test_••••••••4f2a

    Created Nov 3, 2026 · Last used 2 minutes ago

  • Reporting key

    Read only
    lz_test_••••••••9c1e

    Created Oct 21, 2026 · Last used yesterday

Rate limit, this minute0 of 120 requests

The limit resets at the start of each minute.

Imprint: the whole platform, with your name on it

Imprint is the Aevora platform carrying your name, your colours and your domain. Your labels and artists sign in to your brand to upload releases and read their statements, and there is no interface for you to build or maintain.

Type a name and pick a colour to see the idea.

  • Your domain on the dashboard, emails and landing pages
  • Logins for your labels and their artists
  • Catalog, delivery and royalty accounting included

Brand your platform

Live preview
Brand colour
Appearance

app.northfield.com

NNorthfield

  • Releases
  • Catalog
  • Royalties
  • Analytics

Releases

New release

Streams this week26,810

  • Night DriveMira KayaLive in 34 stores
  • Paper LanternsKite & LanternIn review
  • Low TideSable RowDraft

Which way in suits you

Both routes run on the same engine, so the choice is about who builds the interface. You can start with one and add the other later.

What you get
Engine: endpoints and a sandbox. Imprint: a working platform.
What you build
Engine: your own interface. Imprint: nothing.
Where your brand shows
Engine: wherever your product puts it. Imprint: on the dashboard, emails and landing pages.
What you need
Engine: developers. Imprint: a name, your colours and a domain.
Choose it when
Engine: distribution is one feature of a product you already run. Imprint: distribution is the product, and you want it under your name.

Three add-ons for either route

These sit on top of the engine and can be added whichever way in you choose.

Stream Radar
Flags streaming patterns that look artificial, so you can look into a track before a store raises it with you.
Preflight QC
Checks audio, artwork and metadata before a release goes to review, and tells you what to fix.
MCP server
Connects an AI assistant to your catalog, so you can ask about releases and make changes in plain language.

Questions about white-label and the API

No. They run on the same engine, so you can use Imprint for your labels and call Engine for the work you want to automate.

Yes. The API docs are open to read, and the plans for Engine are published on the API pricing page.

Yes. Engine includes a sandbox, so you can build and test before a release is sent anywhere.

Yes. Import it through the API or as DDEX files. Metadata is validated as it comes in.

Read the reference, then decide