Download. Open. Set up.
Choose your computer, open the wizard and decide where Nomiarch will run. You review your configuration and approve a plan before the system is created.
The new infrastructure-only path creates or adopts a VM first. No model, Core bundle, GPU or AI agent is required. For a Local evaluation, the defaults allocate 2 vCPUs, 8 GB of memory and 40 GB of storage; allow additional host space for downloads.
The desktop apps are unsigned, and the Mac app is not notarized. Your computer may show a warning or block the app. Real customer VM installation and physical air-gap testing remain under evaluation.
1. Download and open the wizard
Set up on Windows
For Windows 11 Pro, Enterprise or Education on Intel / AMD with Hyper-V. Windows Home and ARM Windows are not supported in this preview.
- Download the app above, then open NomiarchSetup-windows-x64.exe from Downloads.
- Install Canonical Multipass and enable Hyper-V through your approved Windows setup process before Local provisioning. Then choose Set up infrastructure — Local, On-premises or Cloud (no AI yet).
- Use the Canonical installation guide for VM support. Windows may require administrator approval and a restart.
- The Local infrastructure flow now offers Check your computer and Install VM support. After installing it, choose Check again; Continue becomes available when the check passes.
This unsigned preview may trigger a Windows security warning. On a managed computer, ask your IT administrator whether evaluation is permitted. Keep Windows security protections enabled.
Set up on your Mac
Open Apple menu → About This Mac. If you see Chip with an Apple chip name, choose Apple silicon. If you see Processor with Intel, choose Intel Mac. Help identifying your Mac ↗
Download for Apple chips ↗
For Macs with an Apple chip.
INTEL MACDownload for Intel Mac ↗
For Macs with an Intel processor.
- Download the ZIP for your Mac, then double-click it in Downloads to extract the app.
- Move NomiarchSetup to Applications and double-click it.
- If Apple shows “NomiarchSetup” Not Opened, follow the steps below.
Apple could not verify NomiarchSetup?
This preview is unsigned and has not been notarized by Apple. If you downloaded it using this page and trust it for testing on your Mac, you can allow this app:
- Click Done on the warning.
- Open Apple menu → System Settings → Privacy & Security.
- Scroll to Security. Find the NomiarchSetup message and click Open Anyway.
- Confirm with Touch ID or your password if requested, then click Open.
This saves an exception for NomiarchSetup. Apple's official opening instructions ↗
If the button is missing, try opening the app once more and return to this settings page. On a managed Mac, ask your IT administrator if the option is restricted. Keep your Mac's security protections enabled.
For Local provisioning, the wizard checks for Canonical Multipass. Open the app and choose Set up infrastructure — Local, On-premises or Cloud (no AI yet). Use Install VM support on the computer-check screen if it is missing, then Check again. Actual provisioning requires it.
Set up on Linux
The reference desktop is Ubuntu 24.04 on Intel / AMD. Other Linux distributions are not yet qualified for this preview.
- Download the app above. In your file manager, open its properties and allow the file to run as a program.
- Open NomiarchSetup-linux-x64 and choose Set up infrastructure — Local, On-premises or Cloud (no AI yet).
- If VM support is missing, install Canonical Multipass through your approved software manager. Reopen Nomiarch Setup after installation.
Linux VM support is installed separately in this preview. Canonical's installation guide ↗
Release notes and download checksums ↗
2. Choose the infrastructure and Git service
Choose Set up infrastructure — Local, On-premises or Cloud (no AI yet). Enter project and environment names, such as nomi-test and evaluation.
- Local: creates a dedicated Ubuntu VM on this computer with Multipass.
- On-premises: adopts a dedicated Ubuntu 24.04 host or VM your organisation provides over trusted SSH. It does not create or delete that host.
- Cloud: Azure is the only implemented provider. It creates a private VM, storage and network configuration.
Select GitHub SaaS (github.com, including Enterprise Cloud) or your existing GitHub Enterprise Server. Both require a private configuration repository, successful validation and a separate human reviewer. Selecting Enterprise Server does not install or license a Git server.
Choose Restricted connected for a normal first Local test. Fully disconnected requires Local or On-premises and internal Git; the wizard rejects Azure or GitHub SaaS in that mode.
3. Prepare infrastructure files
Local setup admits the matching Ubuntu image and VM-support installer. Choose Download and verify automatically on a connected computer, or Use files I brought into this environment inside the boundary. Missing or altered offline files stop setup without a download.
The infrastructure path does not download a model or Core bundle. On-premises requires an SSH private key and an out-of-band enrolled known_hosts file. Keep both outside the configuration repository.
4. Review, validate and approve
- Set capacity and target-specific settings. Select Create my configuration and inspect the generated folder. Recipe 0.4.0 has scope infrastructure and no runtime/model pins. No VM is created yet.
- Create the dedicated private repository and open a configuration PR using the steps below.
- Wait for nomiarch-validate, independent review and authorized merge. Enter the merged PR number.
- Choose Prepare deployment plan. Review the exact destination, capacity, network policy and resource actions. Planning creates no VM.
- Choose Approve this plan and establish the infrastructure. Keep the app open while it provisions and verifies. Azure resources incur charges until removed.
Plans expire after one hour and are single-use. Reopening a configuration offers Review the saved plan for an unexpired plan. An expired or invalid unused plan can be retired with its evidence retained, then replaced through fresh checks and explicit approval. Provisioned or uncertain runs cannot use that shortcut.
5. Confirm infrastructure readiness
Expect Infrastructure ready, a recorded inventory and application status not-installed. There should be one retained VM for Local/Azure, or the recorded adopted host for On-premises. No model or AI agent has been installed.
Choose Manage an installation → Verify. It checks OS, capacity, administration and the applicable network boundary. Azure checks the OS filesystem separately from the declared data disk. Reopening setup must not create duplicate resources.
Dev7 certificate fix and scenario tests
Dev7 uses your operating system’s certificate store for HTTPS downloads and repository access. Certificate and hostname verification remain enabled. Each platform package must pass real HTTPS download checks before release. If your organisation uses an HTTPS inspection proxy, its CA must be trusted through your administrator’s normal OS setup.
Follow the end-to-end acceptance guide: all installation scenarios and expected results ↗. The guide covers Local, On-premises and Azure with SaaS or Enterprise GitHub, connected/disconnected combinations, review gates, resume, verification and removal. Automated scaffold checks cover 14 supported combinations; live customer deployments remain acceptance work.
Before moving to models and agents, test one real Local installation, plan resume/expiry, verification, backup/recovery and separately approved removal. Automated tests and packaged scaffold checks have passed; real customer deployments, GitHub/GHES integrations, physical disconnection and clean-host recovery still require acceptance testing.
Azure prerequisites
Select Cloud → Microsoft Azure. Sign in through Microsoft's device-code page, then choose the subscription, region, VM size and a privately reachable subnet. Your administrator must supply the private route and management CIDR. The wizard does not create a VPN gateway or Bastion and does not open public SSH. Azure platform/control-plane dependencies mean this is restricted connected, not a physical air gap.
Repository checks and independent human approval
- Use a dedicated test repository and a designated human reviewer other than the proposer. Your GitHub service must support protected private branches and Actions validation.
- Enter the bootstrap token in the app, with permissions for repository creation/protection, contents/workflows, PRs and reading check results as required by your server. It stays outside Git and model context.
- Select Create a NEW private customer repository, then Open a configuration pull request.
- Confirm the required nomiarch-validate check succeeds. Have the designated human approve the final commit and authorize its merge.
- Enter the merged PR number. The controller rechecks contents, protection, the newest trusted validation result and final-commit human review before execution. Separate plan approval is still required.
The executor is a human-operated desktop controller. This preview does not claim an automated deployment pipeline. Future Nomi agents must have no merge, policy-administration or infrastructure-write authority.
GitHub Enterprise Server
Supply your existing server's root HTTPS address, for example https://git.company.internal, repository owner, reviewer logins and server-issued token. If needed, select its public CA certificate and verify the fingerprint with your administrator. Never supply a private CA key. The server must resolve only to supported private addresses; TLS, hostname and direct-routing checks remain enforced.
Provide an internal, unprivileged validation runner labelled nomiarch-validation with Python 3.11+ and the admitted checkout action. It must have no deployment credentials. Keep Git, identity services, DNS, time, reviewers and validation dependencies inside a fully disconnected boundary.
Models and agents come later
This milestone ends at infrastructure readiness. Models, Nomi Core, specialized agents and the AI request dashboard are later reviewed changes. Existing Core (preview) setup paths remain available for older workflows; they still use admitted Core 0.1.0.dev3. Switching between these flows resets the setup mode in dev7.
Backup, recovery and preview limits
Infrastructure status and backup exports reviewed configuration and controller records. The current desktop export is unencrypted and omits sensitive Terraform state and logs. It is not a complete Azure recovery backup. Preserve the private controller directory and keys separately with your approved protection and test clean-host recovery before relying on it.
Application install/upgrade/repair are later operations for infrastructure-only foundations. Older Core installations retain their existing maintenance workflow. Do not use a Core database backup as infrastructure recovery.
Fully disconnected evaluation
Admit the desktop app, OS image, VM-support tools, internal validation dependencies and trust material through the site's controlled transfer process. Use the infrastructure flow on a matching connected staging computer to prepare its image files; the home-screen general offline-kit action belongs to the older Core flow and may include model/runtime files.
Choose Fully disconnected and GitHub Enterprise Server on Local or On-premises. Use the admitted local files. A firewall or blocked probe does not prove an air gap: the site must disconnect external routes and qualify its administration and transfer boundary. The wizard does not disconnect Ethernet, Wi-Fi or radios.
Finish the test with reviewed removal
Retain needed records and backups, then choose Remove selected VM. The removal requires its own PR, independent review, merge, saved plan and explicit approval. Only the recorded created VM/resources may be removed. Adopted on-premises hosts are never deleted by Nomiarch.
If setup stops
For macOS launch warnings, follow the app-specific opening steps. If the Local computer check reports missing VM support, use Install VM support (macOS/Windows), finish the installer, then Check again. On Linux, install Multipass through your approved package manager.
Keep the failed run directory, logs and any partial state. Use Manage to inspect it; do not create another foundation to conceal a partial deployment. This preview is unsigned and customer-environment qualification is still pending.
Infrastructure bootstrap guide ↗ · Advanced testing and recovery ↗
Desktop 0.1.0.dev7 · Core 0.1.0.dev3 · Windows, macOS and Linux preview