● Unity Application Framework
Ship Unity applications on Molca Core.
Runtime bootstrap, dependency injection, events, networking, settings and content delivery — one licensed package, served from the Molca registry and managed from this control plane.
Inside the editor
One home for the whole framework
The Molca Hub is where a team configures the project, watches its health against the control plane, installs signed add-ons, and works with the in-editor assistant — instead of hunting through scattered inspectors and menus.
Run the preflight checks, then build if they pass.
It's running now:
The three steps will execute: preflight → content-verify → build. Let me know when you want a status check.
Action · mode Edit · revert None · confirms before running
Authorized: 'preflight-to-build' is in the automation action allowlist and may run under the active profile.
Rendered from the shipped interface — pick a workspace above to look around.
Getting started
Install Core in a Unity project
Two pieces of configuration. After them, Package Manager treats Core like any registry package — version list, Update button, semver ranges.
-
Declare the registry
In your project's
Packages/manifest.json.Packages/manifest.json { "scopedRegistries": [ { "name": "Molca", "url": "https://unity.molca.id/registry", "scopes": ["com.molca"] } ], "dependencies": { "com.molca.core": "2.5.8" } }Pinning an exact version keeps builds reproducible — Package Manager offers newer releases as they ship, and semver ranges work normally.
-
Authenticate
In
.upmconfig.tomlin your user profile — not the project.%USERPROFILE%\.upmconfig.tomlon Windows,~/.upmconfig.tomlon macOS and Linux..upmconfig.toml [npmAuth."https://unity.molca.id/registry"] token = "msa.msa_….…" alwaysAuth = true
Mint your own token. Any member of a Molca license can create one from the dashboard under Trust → Registry access — no owner, no email. Use one per machine and one per CI job; a token you can revoke on its own is worth more than one everybody shares.
The download is license-gated, so a lapsed or suspended license stops resolving new
installs. Keep the Library package cache warm in CI images if builds need to
outlive license churn.
The platform
What you get
Core, from the registry
The framework itself, versioned and license-gated. Upgrades arrive as a Package Manager update rather than a manifest edit, and every release is reproducible from a pinned version.
Add-ons, from the Hub
Sequence, Sentry, Figma, GitHub and Pipeline install from Molca Hub › Add-ons — signed, and resolved against your Core version.
Project dashboard
Builds, team access, content releases and project health for every project on your license.
Molca Remote
Watch a running editor, review findings and drive approved automations from a phone or a browser.