Early access

InertiaX is available through private early access. Request access at inertiax.dev; approved requests get a sign-in link to your portal by email.

Before installing

Sign in to portal.inertiax.dev, accept the license and create a registry key. Then, in your application’s directory, run the Connect the registry commands the portal’s Registry keys page shows for Composer and for your JavaScript package manager. Once both can resolve the packages, continue with Table installation.

Early-access versions may include breaking changes, incomplete behavior or documentation, and registry/service interruptions. Evaluate them before production-critical use. Early access has no fixed duration, general-availability date or SLA; the Terms of Use describe how access can change or end. Follow replacement instructions by email if credentials or registry endpoints change.

License

Each InertiaX package includes the InertiaX Early Access Software License Agreement in its LICENSE.md file.

Store credentials

Keep registry keys out of source control, screenshots and shared output. A project file that holds one, such as auth.json or .npmrc, belongs in .gitignore. One key serves Composer and npm. Name each key after where it’s used, such as CI, so you can rotate or revoke it on its own.

CI access

Store credentials in your CI system’s protected secret store. Expose them only to the install step, disable command tracing, and avoid printing authentication configuration. Create temporary authentication files outside the checkout and remove them after every outcome.

In CI, run the portal’s Connect the registry commands with the key read from that secret store. For installation failures, see Table installation troubleshooting.

Get support

For help with InertiaX or your account, email contact@inertiax.dev; for an error, include the details it needs. Public progress and interruption notices are posted by @yhteamdev. To report a vulnerability, see Security.