Originally published October 1, 2026 · Updated October 10, 2026

Qwerty deployment guide

Choose the test Macs, prepare the package and model, then check installation and everyday tasks before a wider rollout.

Qwerty AI, Inc. · Local AI and agents for government, military and enterprise Mac fleets.

Choose the Macs and owners

Use Apple Silicon Macs with macOS 14.4 or later. Record the chip, RAM, free storage, macOS build, MDM, users, network setup and restrictions, permitted files and task. Check the approved model's memory and storage needs; one minimum does not cover every model profile.

Name the IT owner, security reviewer, person responsible for the workflow and support contact. Agree on the group of test Macs, what counts as a successful result, retention, schedule and support terms.

Prepare and install in this order

  1. Check the release manifest, hashes, signatures and notarization. Confirm where the package and model came from (provenance), and check model promotion records.
  2. Apply the approved managed configuration and operating policy.
  3. Install the supplied app package through your authorized installation method.
  4. Provide the model authorization, entitlement, public trust material and the exact model files.
  5. Check that the installation is ready, then try representative tasks before adding more Macs.

Test your installation method

Package and configuration-profile paths are documented for Jamf Pro, Microsoft Intune, Kandji and Workspace ONE. Test enrollment, profile delivery, installer behavior and restrictions in your own tenant. These documented paths are not certified integrations.

For an offline transfer, verify the files and follow your organization's handling rules for the restricted environment.

Check the results before rollout

Agree on the schedule

The 90-day window is a planning framework for choosing tasks, installing, testing and deciding what to do next. Agree on actual dates, the group of test Macs, support and success criteria for your evaluation. Finish with a decision to expand, change the setup or stop, and keep the results behind that decision.

Prepare for recovery and removal

Record the app version, release hash, profile, hardware, mode, workflow, UTC time and approved diagnostics. Follow the supplied instructions for restart, repair, registry verification, updates and rollback. Preserve local data unless an authorized retention decision calls for deletion.

Check the release you will deploy

The retained engineering report does not authorize a production deployment. Before a wider rollout, check production signing, notarization, model promotion records and customer acceptance for the package you received.