Skip to content
The Fenophone

Developer docs

The Fenophone runtime license

Standard terms for embedding the engine in a game — free for jams with a credit, a one-time per-title license to ship. Read in three minutes.

Status: draft

DRAFT — pending counsel review. This document is the standard written agreement for embedding the Fenophone engine in another product. Until countersigned by the owner for a named title, it grants nothing — except the self-executing game-jam / evaluation tier in §5, which is granted by this document itself, without countersignature. Everything else exists so the offer, the price shape, and the obligations are on the record and reviewable. Contact: through the waitlist.

1. What this licenses

The Fenophone adaptive runtime: the compiled engine core (its C interface, or the Wasm build of the same core), embedded inside one named game or interactive product ("the Title"), plus the launch scaffold/voice packs it ships with. Nothing here licenses the source repository, the web product, or the DAW plugin (each has its own terms).

2. Grant (per Title, one-time — the own-it-forever shape)

On payment of the per-Title fee and countersignature, the licensee receives, for the Title:

No royalties, no revenue share, no phone-home, no DRM — the runtime never gates the Title's players.

3. Conditions

4. Fee shapes (working assumptions — validated before any public price)

5. Game-jam / evaluation tier (self-executing — no countersignature required)

As the one exception to this document's draft status, the owner grants the following license now, to anyone, by this document itself — no contact, no payment, no countersignature:

6. Warranty & liability

The runtime is provided as is; liability is capped at the fee paid (counsel to confirm the enforceable form per jurisdiction). The licensee ships the Title; the owner ships the engine.

7. Wind-down

If the product winds down, already-countersigned runtime licenses survive unchanged (they are perpetual), and the owner's published wind-down guarantee commits to a final engine build the licensee may keep redistributing inside the Title.

Ready to build?

Jam and prototype builds can start today under §5 — and for SDK access or a commercial title, the waitlist is the door.