Install and complete first launch

What this guide is for

Use this guide when you install Arizmic on a new computer or open it for the first time after an update. The goal is simple: confirm that the package is authentic, let the launcher start the local services, and verify that the workstation is ready before you import data or run a Strategy.

Arizmic is desktop software. The application, local services, projects, and most working data run on your computer. A browser-like workstation window is part of the desktop application; it is not a hosted Arizmic account.

Availability before release

The public preview does not provide installers. Windows and macOS packages become available only after the release build has passed signing, platform, clean-install, first-launch, update, and uninstall checks. Do not download an Arizmic package from an unofficial mirror or bypass an operating-system warning for an unverified build.

When downloads open, the release page will state the supported operating systems and architectures, the version, the publisher, and the package checksum. Linux availability is listed separately because its packaging and desktop integration differ from Windows and macOS.

Before you install

You need:

• a supported computer and operating system;
• permission to install desktop software;
• enough local storage for the application, source data, Prepared Data, Run Outputs, Study Results, and Notebook projects you intend to retain;
• a writable folder for Arizmic application data; and
• network access for activation, updates, and any external data, model, or broker service you choose to use.

See System requirements for the supported release matrix. External provider accounts and credentials are not required merely to open the workstation.

Verify the package

Download only from the official Arizmic website or a release link it provides. Before opening the installer:

1. Confirm that the version and operating system match your computer.
2. Check that the operating system identifies the expected publisher.
3. Compare the package checksum when the release page provides one.
4. Stop if the signature is missing, invalid, or belongs to a different publisher.

A checksum confirms that the downloaded bytes match the published package. It does not replace code signing, notarization, or the operating system's trust checks.

Install on Windows

1. Close any older Arizmic process.
2. Open the signed Windows installer.
3. Review the publisher shown by Windows.
4. Choose the supported installation options and complete the installer.
5. Start Arizmic from the installed shortcut or Start menu entry.

Do not move files out of the installed application folder or start internal executables directly. The launcher establishes the supported runtime, service, and workstation relationship.

Install on macOS

1. Close any older Arizmic process.
2. Open the notarized macOS package supplied by Arizmic.
3. Move or install the application as instructed by the signed package.
4. Open Arizmic from Applications.
5. Confirm that Gatekeeper accepts the identified developer and notarization.

Do not remove quarantine metadata or override Gatekeeper for a package that has not passed the published release checks.

Let the launcher reach Ready

The launcher starts the required local services and opens the matching workstation build. During startup it may show phases such as preparing, starting, checking, or reconnecting. Wait for Ready before opening a second instance or changing connection settings.

If the launcher reports an error, use the displayed action first. Repeatedly starting new instances can leave multiple local processes competing for the same ports or data folder.

Choose and verify application storage

Arizmic keeps application data separately from the installed program. This lets you update or remove the application without silently deleting projects and retained outputs.

On first launch, confirm the selected application-data folder in System & Jobs -> System Settings. The folder must be local, writable, and suitable for the volume of data you plan to store. Avoid temporary folders and locations that another application may clean automatically.

Changing the folder later affects where future work is written. It does not silently move existing content. Back up and migrate deliberately.

Check the workstation connection

Open System & Jobs -> Information and review the workstation, API, and app identity. Then use Check Workstation when the action is available.

The check answers three separate questions:

• is the launcher-managed workstation reachable;
• is the local API compatible and current; and
• is the visible app build the one the launcher expects?

If an Update Workstation or Use launcher connection action appears, use that action and repeat the check. Do not copy an old local origin from a previous session into configuration.

Review system readiness

In System & Jobs -> Information, confirm the detected operating system, processor, memory, and storage. These values describe the current computer; they do not guarantee that every Study will fit within its resources.

In System & Jobs -> System Settings, review worker and storage limits before running large work. Start with conservative settings. A higher worker count can increase memory pressure and storage contention even when the computer has more processor cores.

Benchmarks are optional. Use System & Jobs -> Benchmarks to compare bounded workloads on this computer, not as a promise of production speed or live execution latency.

Confirm Jobs and Activity

Open System & Jobs -> Jobs. An empty queue is a valid first-launch state. The page should still render its controls and status without an API error.

Open Activity Log. It may be empty, but it should be readable. Activity is the place to inspect application events and failures; it is not a substitute for the Result produced by a Study.

Run a small navigation check

Before importing a large file, open these destinations once:

1. Data Manager -> Catalog
2. Signals
3. Strategies
4. Studies
5. Results
6. System & Jobs -> Jobs
7. Activity Log

Each destination should load without a console-style error panel. Empty libraries and tables are expected on a new installation.

If first launch is blocked

First-launch checklist

You are ready to continue when:

• the verified launcher reports Ready;
• the application-data folder is writable and has suitable free space;
• Information shows a coherent workstation, API, and app identity;
• Jobs and Activity Log open normally; and
• the main destinations load without a connection error.

Next, read Workstation Basics, then complete Your First Strategy Run.