Mozaik extension platform

Mozaik is a multi-tenant e-commerce platform for the Turkish market. Everything provider-specific is an extension ("Eklenti" in the merchant UI): payments, cargo, e-invoice, marketplace sync, messaging, reporting. Nothing provider-shaped is default — a fresh store has zero listed extensions, and Mozaik's own providers (iyzico, Geliver, havale, kapıda) are installable extensions built on the exact contract documented here.

This site is generated from the live platform registries at build time: the manifest schema, every command, the admin zones, the hook contract, the limits table and the first-party catalog are emitted from source, never hand-copied. Hand-written pages (these concept pages) may only name things that exist — an unresolved reference fails the build.

Start here

1. What is an extension — the manifest, runtimes, and what stays core.
2. Runtime model — platform · sandbox · external, honestly.
3. Install lifecycle — gallery → consent → extension.install → configure → extension.enable.
4. Provider kinds — payment, shipping, cargo, e-invoice, channel, messaging, reporting.
5. Building an extension — how first-party extensions are laid out today.
6. For agents — llms.txt, .md variants, schemas.

Reference

• Extension manifest · Commands · Admin zones · Checkout hooks · Limits · Scopes · Storefront sections · First-party catalog

Non-negotiables

• Commands are the ONLY write path. No extension SQL, no extension-defined inbound routes, no free HTML injection into the admin or the storefront shell, no per-store code forks.
• Money never flows through Mozaik: every provider extension uses the merchant's own account (secrets are write-only and sealed).
• Every first-party extension is included in the flat ₺49/ay — installable never means paywalled.