Skip to main content

Start Here

This section is for platform builders.

If you operate a game, application, marketplace, tool, or service and want to support user-generated content without giving up control, this is for you.

You are not expected to adopt a new platform. You are not expected to change your business model. You are not expected to surrender users, UX, or revenue.

OGAL exists to give platforms stronger primitives, not replace them. If you want to learn more about using OGAL, check out the OGAL Guide.

If you want quick definitions of core terms, check the Glossary.

Proof in production: Token Toss is a working reference implementation proving the SDKs and protocols in production. Download the game from Ghiblify Games.

What This Is​

OGAL is a neutral ownership and provenance layer.

It does:

  • define canonical asset identity
  • enforce ownership and update rights
  • preserve provenance across applications
  • allow free reuse by default

You integrate OGAL the same way you integrate a database or protocol. It becomes part of your internal system, not a competitor.

What This Is Not​

It does not:

  • host assets
  • run a marketplace
  • enforce monetization
  • dictate UX
  • capture users

OGAL defines what is true.

Who This Is For​

This documentation is written for teams that:

  • Run games or interactive applications
  • Host creator or user-generated content
  • Care about long-term asset ownership and trust
  • Want interoperability without lock-in
  • Need to preserve control over UX, monetization, and users

If you are looking for a hosted marketplace, this is not that.

What Problem Platforms Actually Face​

Most platforms do UGC because it works. Most platforms struggle because UGC creates long-term liabilities.

Common pain points:

  • Ownership disputes and takedown risk
  • Platform-specific asset silos
  • Rebuild costs across products
  • Trust issues around royalties and accounting
  • Fear of enabling competitors by opening systems

These problems are structural, not operational.

OGAL addresses them at the infrastructure layer.

How Platforms Use OGAL​

At a high level:

  1. Your platform integrates OGAL via tooling (Unity first)
  2. Assets minted or referenced by your users gain canonical identity
  3. You read ownership and permissions from OGAL
  4. You decide how assets are surfaced, monetized, or gated
  5. Assets remain portable across other OGAL-aware platforms

Nothing forces your hand. Every choice remains yours.

What You Keep Full Control Over​

Platforms retain full authority over:

  • User experience
  • Business model
  • Monetization logic
  • Pricing
  • Discovery and ranking
  • Moderation and policy
  • Distribution strategy

OGAL does not override platform decisions. It removes ambiguity around what is true.

Optional Composition and Monetization (OPP)​

If you want structured monetization across multiple assets:

  • Use OPP to package assets into executable bundles
  • Declare usage rules and revenue intent via an SBOM
  • Enforce payments in your own application layer
  • Avoid manual accounting and partner disputes

OPP is optional. OGAL works without it.

Free reuse is always allowed.

Why This Does Not Create Lock-In Risk​

Lock-in comes from:

  • proprietary formats
  • centralized registries
  • forced marketplaces
  • opaque accounting

OGAL avoids all of these.

  • Assets are portable
  • Ownership is public
  • Reuse does not require permission
  • Markets compete on UX, not rules

You can leave at any time. Your users’ assets do not disappear if you do.

Adoption Model (No Big Bang Required)​

Platforms typically adopt OGAL in phases:

  1. Read-only
    Verify ownership and provenance for select assets

  2. Mint-aware
    Allow users to mint or register assets with canonical identity

  3. Reuse-enabled
    Pull OGAL assets created elsewhere into your experience

  4. Optional monetization
    Use OPP where it creates new value

Each phase is incremental. No migration cliff exists.

One Sentence Summary​

OGAL lets platforms support open, portable user-generated assets without becoming open platforms themselves.

That separation is the point.

Success Checklist​

Next Steps​

If you want to understand the internals, architecture docs are available — but not required.