m Miyan App
All systems operational
Public site

Miyan’s control plane

Make the site. Keep the control.

One quiet place for the people responsible for a Miyan instance — from the first domain to the next published revision.

Account access

Sign in with your access key

Your master issues the key for your Miyan account. It identifies your control-plane role and the instances you can manage.

Keys are only kept in this browser’s memory for the active session.

Need access? Ask the master who created or manages your Miyan instance.

The working set

What you manage here

  1. 01

    Instances

    Shape each tenant’s website, settings, and publish state.

  2. 02

    Domains

    Attach custom hostnames and inspect their active snapshot.

  3. 03

    Modules

    Choose curated building blocks and their published configuration.

  4. 04

    Storage

    Keep public images, styles, scripts, and catalog files organised.

  5. 05

    Renewals

    See ownership, plan status, and the next renewal before it matters.

The publish path

A site is a hostname-keyed snapshot.

Configuration becomes a small public document. The browser builds the rest from static Miyan modules.

Configure miyan-app instance · modules · assets
Compile runtime context prebuilt in memory
Publish root-assets.w4r.app /user-domains/{domain}.json
Visit your custom domain example.com

Each custom domain and {id}.w4r.app instance loads its own distinct init.json.