Molca MolcaUnity Platform

Built for Unity teams

Your next Unity application. Built on Core.

From the first scene to the next release. Bring your runtime, tools, and content delivery together with one application framework.

Latest release com.molca.core@2.8.1
Molca HubInside the Unity Editor
The Molca Hub window inside the Unity editor. Choose a workspace: Settings, Doctor, or Assistant.
Project Health Needs attention Refresh Open dashboard
1 of 5 areas need attention.Checked 01:54
Connection5 live bindings Healthy
Nothing to do here.
Content1 live channel Healthy
Nothing to do here.
BuildsNothing shipped yet Needs attention
Builds were authorized but none reported an outcome.A build that ended before its token was minted cannot report. Check the Hub build history on the machine that ran it.
Add-ons3 in policy Healthy
Nothing to do here.
RemoteNo active session Healthy
Nothing to do here.
Run Checks Copy Export… Remediation… Errors (0) Warnings (2) Info (7)
▸Scene 6/6 on
▸Async & Lifecycle 4/4 on
▸References 5/5 on
▸Docs 0/2 off
▸General 4/4 on
▸Sequence 1/1 on
Run LogPer-check trace of the most recent run 4.2 s Copy
reference-scope-auditA scene reference resolves through the legacy global scope. Re-point it at the owning scene, or declare the scope on the component.
Workflow Assessment For Use Case
You

Run the preflight checks, then build if they pass.

▸ Thought for ~55 tokens
✓ Approved · Run action: molca_workflow_run
Assistant

It's running now:

Run Open in canvas ↗

The three steps will execute: preflight → content-verify → build. Let me know when you want a status check.

Anthropic claude-opus-5 Reasoning: High
Ask about your project… @ context · / commands
AskAuto PlanAll ~53,221 / 200,000 tok Send
▶ Preflight → Build
Preflight → Build Run project checks, validate content config, then build.

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.

Revoke authorization
1. Preflight critical
2. Content Verify critical
3. Build action · irreversible critical
Save Save & RunRevise in chat

Explore the interface: choose Settings, Doctor, or Assistant.

01 / Build on a shared foundationBootstrap, injection, events, and networking.

02 / Keep your workflow togetherProject health, add-ons, and an in-editor assistant.

03 / Take control of your releasesVersioned packages and managed content delivery.

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.

  1. 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.8.1"
      }
    }

    Pinning an exact version keeps builds reproducible — Package Manager offers newer releases as they ship, and semver ranges work normally.

  2. Authenticate

    In .upmconfig.toml in your user profile — not the project. %USERPROFILE%\.upmconfig.toml on Windows, ~/.upmconfig.toml on 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

One platform. From editor to delivery.

The tools around your application, connected in one place.

01

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.

02

Add-ons, from the Hub

Sequence, Sentry, Figma, GitHub and Pipeline install from Molca Hub › Add-ons — signed, and resolved against your Core version.

03

Project dashboard

Builds, team access, content releases and project health for every project on your license.

04

Molca Remote

Watch a running editor, review findings and drive approved automations from a phone or a browser.