Windows to Omarchy.
Bring your stuff with you.

No. There is no released kit, supported pilot, reservation, or waitlist position today. The complete journey has not been proven end to end on customer hardware or real customer data. Registering interest may lead to build updates, research invitations, or future pilot information. It is not an order, a promise of access, or permission to try the workflow.

It is a product journey we are researching for people who want to move from Windows to Omarchy without becoming backup or Linux experts. BLUE is a physical personal cloud that saves and verifies supported files. GOLD is the installation key. Then BLUE brings the supported files back. It is not a finished product yet.

Omarchy is the Linux-based computer environment being evaluated as the first destination for this project. On the same-computer journey, it would become your main environment in place of Windows. Some familiar Windows programs may not run there, so application compatibility has to be checked before any switch.

The leading idea is a prepared BLUE storage device and a separate GOLD installation key, with very simple instructions. A customer-kept BLUE is being considered. The exact devices, ownership terms, packaging, contents, shipping method, and whether every offer includes both devices are not final.

A customer-kept BLUE is the leading idea, but ownership, rental or loan terms, return obligations, and what happens to GOLD after the move are not final. Registering interest gives you no ownership right and creates no order.

Not for the basic kit being considered. The intended work happens on your computer with the devices in your hands. Assisted service and preconfigured-computer options are separate ideas, and their shipping or handling process has not been defined.

First, plug BLUE into Windows, choose SAVE MY STUFF, and wait for READY TO SWITCH. Then remove BLUE, insert GOLD, and follow the computer-specific startup and installation steps. After Omarchy starts, insert the same BLUE, choose BRING MY STUFF HOME, review the report, and sign back into your accounts. This flow is planned, not released.

BLUE is being designed to read from the Windows computer and copy supported files onto BLUE. It must not delete, rename, move, or format files on the Windows computer. A prepared BLUE may open a guided application, but the exact Windows prompts are still being tested. If a future bring-your-own-drive option needs to prepare that separate drive, it must explain the change and ask first.

GOLD is not a password or a license code. It is the planned physical installation key. Before installing anything, a released GOLD must confirm READY TO SWITCH, the right computer and BLUE, an untampered release, the intended destination disk, and your deliberate approval. No customer-ready GOLD exists today.

A released GOLD must refuse to change the computer unless the same migration has a fresh, valid READY TO SWITCH result from BLUE. Missing, stale, altered, wrong-computer, or wrong-BLUE evidence must stop the process. Do not test this today. No customer-ready GOLD media or procedure exists.

You would insert the same BLUE used for this migration and choose BRING MY STUFF HOME. A released process should recognize the migration, keep the verified copy on BLUE unchanged, restore supported data without running copied programs, and show what returned or still needs attention. This restore flow is not proven today.

The final BLUE and GOLD connections are not selected. A finished offer must state whether it uses USB-A, USB-C, an included cable, or an approved adapter before you buy. The instructions should also say when to connect power, prevent sleep, remove BLUE, and insert GOLD. Hubs and unapproved adapters may be excluded until tested.

A future release must make the devices visually distinct and cryptographically authenticate the exact approved installer and media. GOLD must reject an altered, stale, withdrawn, substituted, or untrusted release. Use only the device assigned to your migration through an approved channel. None of those controls or the replacement process is proven today.

Do not connect or use it. Color, labels, packaging, filenames, and a support message cannot prove that a device is genuine. A released process must recheck the exact media, migration, computer, authorization, and installation release. Any mismatch must say STOP and use an approved replacement process.

No. Do not build or connect BLUE or GOLD media from this page. No customer kit, installation runtime, or released safety procedure exists today. Wait for an explicitly released, supported product. This page grants no installation permission.

No. BLUE GOLD BLUE is an independent Intent Solutions research project. It is not an Omarchy endorsement, partnership, official migration product, or current offer to distribute Omarchy media. Any future distribution would require the proper technical and legal permissions.

No destination is customer-supported today. Omarchy is the only initial destination under evaluation. Ubuntu, Fedora, Mint, and other systems are outside the first release boundary and would need their own compatibility, restore, usability, and safety testing.

Windows 10 or 11 alone is not enough. The first target is a personal, unmanaged, single-user laptop with an Intel or AMD 64-bit processor, one ordinary internal drive, and an exact model and Omarchy release that have been tested together. There is no supported-model list or customer checker today. Missing, unknown, or unsupported evidence must stop the switch.

Not today. There is no released checker or final supported-computer list. A future non-destructive check should review your exact computer, Windows version, storage, security settings, important apps, and devices, then show what is supported, unknown, or blocked before you buy or change anything.

No customer preview path is promised yet. A temporary boot-time check may be needed to prove hardware compatibility, but that is not the same as a safe trial or dual-boot setup. Do not download or boot installation media from this page. Any future preview must explain its limits and leave Windows unchanged.

They are not part of the first product boundary. The design may support more source computers later, but the first proof is intentionally narrow: supported Windows 10 or 11 computers using Intel or AMD 64-bit processors.

The first target is a personal, non-company-managed computer with one primary user. Work-managed devices, shared systems, and multiple user profiles are outside the initial proof because they add permissions, ownership, policy, and privacy questions. Do not use the kit on an employer's or shared computer unless a later, separately tested process explicitly supports it.

The current standard-user proof cannot read every BitLocker or Secure Boot setting, and no customer elevation path is released. A future client should use the least access it needs and explain any approved administrator prompt before it appears. If a required security or firmware state cannot be checked safely, BLUE must say REVIEW or STOP.

That depends on the exact computer and is not settled. A supported machine may need a guided startup-menu or Secure Boot step. You should not have to interpret raw Linux disk names, guess which drive to choose, or follow generic firmware instructions. No customer-ready startup path exists today.

BLUE may need to identify encryption state, but it must not collect BitLocker recovery keys or silently treat Windows EFS files as ordinary protected data. A locked or uncertain BitLocker volume, or a required EFS file without a tested path, must produce STOP. BLUE's own encryption would not solve access to Windows-encrypted files.

No unreleased process should ask you to disable Defender or antivirus, bypass Windows security, or send anyone a password. A future client may need an approved administrator prompt for specific checks, but that behavior is not proven. An undocumented exception must produce REVIEW or STOP, not instructions to weaken your computer.

The first proof is limited to one straightforward internal Windows drive. Extra internal drives, partitions, attached drives, network shares, and home storage are outside that proof. Their presence must prevent READY TO SWITCH unless a separately tested policy handles them and you review every exclusion.

Both journeys are being considered. The same-computer path would replace Windows after BLUE passes every safety gate. The new-computer path would save from the old computer and restore onto a separately qualified computer, leaving the old machine intact as a fallback. The new-computer option is a future product path, not a current offer.

It can erase the Windows system disk, including Windows, installed programs, settings, and any local data on that disk that BLUE did not protect. Only separately verified, supported data is intended to return. BLUE is not a Windows system image, and no proven Windows rollback exists. That is why GOLD must remain locked until every required safety check passes.

Yes. That remains possible while the product is unproven. Same-computer GOLD is intended to erase Windows, BLUE protects only a defined supported set, and no complete Windows rollback is proven. No customer should attempt the move until verification, independent recovery, and end-to-end destructive testing are released and the exact computer is approved.

Do not expect dual boot. The simple same-computer journey is being designed as a controlled replacement, not a menu that keeps two operating systems side by side. A new-computer journey may reduce the risk of changing the original Windows computer, but it is a future path and has not been tested.

That is not currently promised. BLUE is being designed to protect and restore supported personal data, not to create a complete Windows system image with every program, license, and setting. Reinstalling Windows would be a separate recovery process.

A future released BLUE step should leave Windows and the source files unchanged, so stopping before GOLD should leave Windows usable and does not commit you to a switch. That behavior is not proven in a customer runtime today. Never use GOLD after REVIEW, STOP, or an incomplete or uncertain BLUE step.

No Windows license, product key, or activation transfer is promised. BLUE is intended to protect selected personal data, not a Windows installation. Reinstalling or reactivating Windows would be a separate recovery process.

Do not rely on this research project as a rescue service. A failing drive or unstable computer needs a separate recovery approach, and continued use can make data loss worse. The first product scope is a controlled migration from a working, supported computer.

No. BLUE is not intended to clone the entire Windows system. The first version is being tested for a defined set of supported personal data. It will not recreate Windows, installed programs, every setting, licenses, passwords, or signed-in sessions. A future released process must show an itemized record of what was found, copied, skipped, or needs attention before GOLD.

The initial work starts with the current user's Desktop, Documents, Downloads, and Pictures folders. Other folders, other user profiles, redirected or network locations, application data, and online-only files are not automatically protected. A released flow must list every included, skipped, and blocked location before GOLD. Copy and restore are not proven today.

If a file is only online, BLUE cannot protect it until the actual file is local and verified. A name or shortcut shown in Windows is not enough. No OneDrive, Dropbox, or other provider-acquisition path is released. A future process might ask you to make files available offline, which can use internet access and Windows disk space, but it must never sign in silently or count a partial download. A required file that cannot be obtained and verified must produce REVIEW or STOP.

The final selection experience is not set. A customer should be able to understand and deliberately exclude personal content, but an excluded required item cannot still count as protected. BLUE must show what will be included, what was left out, and whether those choices prevent READY TO SWITCH.

A released process should show what BLUE found, what it protected, what it skipped, and which apps or devices need attention. You should be able to mark the things you cannot live without as critical. An unknown or unsupported critical item must produce REVIEW or STOP before GOLD. This customer review is not proven yet.

Not automatically. BLUE may identify programs and classify the likely path as a native Omarchy app, a web app, an alternative, or unsupported. It will not copy Windows program files and pretend they will work. If an essential program has no acceptable path, the result should tell you to stop before GOLD.

No named application or compatibility checker is customer-supported today. Windows program files will not move. Each exact edition, version, required feature, license, peripheral, and file format needs a truthful answer. A web version, Linux app, or alternative is not automatically equivalent. If something essential is unknown or unacceptable, do not switch.

It is not automatically protected just because it feels like one of your files. Each type needs a supported discovery location, a verified copy, and a proven destination app or import path. Unknown or unsupported critical app data must produce REVIEW or STOP before GOLD.

Restoring a file and being able to use it are related but different questions. Common formats may open in native or alternative apps, but unusual, proprietary, damaged, or application-specific files may not. Compatibility testing must cover both the file copy and the destination app needed to use it.

Expect to sign in again. BLUE must not migrate browser passwords, cookies, sessions, autofill or payment data, Windows Credential Manager material, Git credentials, SSH private keys, BitLocker or EFS recovery keys, cloud credentials, or secret environment values. If a secret appears in BLUE, a report, a log, or an AI context, stop and do not share that artifact.

Bookmarks and other safe familiarity data may be translated when a supported path is proven. Email, contacts, calendars, and locally stored archives are not currently promised and require a separately proven path. Expect to sign in again. Your Windows account, every preference, account secrets, and live sessions will not simply become an Omarchy account.

Supported personal folders should return to predictable places, and selected familiarity items such as wallpaper, bookmarks, fonts, and safe settings may be translated. The goal is to reduce the shock of switching, not to make Omarchy pretend to be Windows. A restore report must show where things went and what still needs attention.

BLUE should never silently skip it and still say everything is safe. Supported exceptions must be listed with a plain-language reason. Important unreadable or unavailable content must produce REVIEW or STOP until it is recovered, deliberately excluded, or handled through an approved process.

There is no universal guarantee. Compatibility must be checked for your exact computer and Omarchy release, including Wi-Fi, Ethernet, graphics, displays, audio, keyboard, mouse or trackpad, webcam, Bluetooth, printers, and anything else you depend on. An unknown or unsupported critical device must produce REVIEW or STOP before GOLD.

Restore is being designed to avoid silently overwriting an important file, reject broken or unsafe restore instructions, record every conflict, and support a safe retry. An interrupted restore must not damage the verified copy on BLUE, place files outside the intended restore area, run copied programs, or claim that everything returned. The exact recovery choices still need controlled testing.

Restore must stop new writes, leave BLUE unchanged, preserve existing or newer destination files, and report exactly what remains. It should resume only from a verified checkpoint after space is made safely available. That failure and recovery path is not proven today.

A future released restore must end with an itemized report showing what returned, what was skipped or conflicted, what needs another app, and which accounts need you to sign in again. Missing or uncertain items must stay visible. A progress bar or copied-file count alone is not proof that the restore is complete.

READY TO SWITCH must mean more than a percentage, hash, signature, or completed progress bar. A future released process must account for the required inventory, independently verify the obtained file contents, check source health and capacity, use current compatibility evidence, and bind the result to this migration, computer, BLUE, and exact destination release. Missing, stale, conflicting, or unknown required evidence must produce STOP or REVIEW.

Only the explicitly approved system drive should ever be eligible. The design requires positive computer and drive identification, protection of BLUE and every other removable device, and a final authorization check. If the intended drive cannot be identified with certainty, GOLD must stop. Those controls are not yet proven on real customer hardware, so GOLD is not ready for customer use.

The intended behavior is to stop without declaring success and preserve both Windows and the last verified BLUE copy. A retry must identify the same BLUE, validate its durable checkpoint, discard incomplete work, detect files that changed, reverify the full required set, and issue a fresh result. Old READY evidence cannot survive an uncertain retry. This still needs fault-injection testing.

The exact rule is not set. Files can change while you work, so a released process must explain what you can keep using, when apps should close, when the computer must stay awake or plugged into power, and when BLUE is safe to remove. It must recheck required data before READY TO SWITCH. Do not unplug BLUE during an active or uncertain operation.

Yes. Do not treat one local BLUE copy as disaster protection. A future customer release must define an independent backup and recovery requirement before GOLD. Until that requirement and recovery path are tested and published, do not proceed with a destructive migration.

Do not. READY TO SWITCH must bind one migration, computer, BLUE, and destination release. Reuse and reset rules are not proven, and a released GOLD must reject a missing, stale, altered, wrong-computer, or wrong-BLUE record. Never swap devices or erase the only verified copy.

An interrupted installation can leave the computer without a working operating system after Windows has been removed. There is no proven rollback that recreates the original Windows installation, programs, licenses, settings, or startup state. BLUE is intended to preserve the verified supported files, but it is not a complete system image and does not repair the computer. Recovery and retry rules must be proven on disposable hardware before GOLD is ready.

No safe stopping procedure is proven yet. Do not start GOLD until a released process tells you exactly when and how stopping is safe. Once installation begins, never improvise by unplugging a device or shutting down the computer; follow only the released recovery instructions.

A local device can be lost or fail, so BLUE must not be described as permanent or disaster-proof storage. Encryption, recovery copies, replacement, and failure handling are still being proven. Losing BLUE after Windows has been replaced could be serious, which is why the commercial design cannot move ahead without a tested recovery story.

No replacement policy, price, turnaround time, or recovery service exists today. A replacement process would have to preserve the migration and device binding. A new device cannot recreate files when the lost or failed BLUE held the only copy.

The provisional design encrypts file contents, filenames, catalogs, and reports while keeping private recovery material separate from BLUE. Intent Solutions would not keep an escrow copy or backdoor. Some basic media facts, such as approximate sizes or counts, may remain visible. If every separate recovery package is lost, the data may be permanently unrecoverable; if one is stolen, that migration may be exposed. This is not a production guarantee yet.

The design aims to keep your data recoverable through a documented, non-proprietary path where practical. The final storage format, authorized decryption tool, recovery package, and customer recovery steps are not proven. Do not assume independent recovery is available today, and never treat one BLUE device as your only backup.

BLUE is physical local storage that stays with you, not an internet cloud, with file contents kept local by default. Any optional network step must disclose exactly what leaves the computer and must not send file contents, credentials, keys, or browser secrets by default.

The migration keeps file contents on your computer and BLUE. Support must use redacted reports and must not ask for personal files, passwords, recovery keys, or unrestricted computer logs. Any optional remote access would require separate, explicit consent and published limits.

No customer support or remote-access channel exists today. A future option would need verified identity, separate consent for that session, minimum access, visible and revocable control, redacted diagnostics, and an audit record. Support could not request secrets, override REVIEW or STOP, approve GOLD, or choose a disk to erase.

Migration must treat saved content as untrusted. The restore design must not automatically run migrated programs, scripts, or unknown executables. Malware scanning and customer guidance still need a defined, tested policy, so BLUE cannot promise that every saved file is harmless.

Stop. BLUE is not malware cleanup or emergency data recovery. Suspected compromise, unexpected file changes, or ransomware must prevent READY TO SWITCH and GOLD. Copied material must remain untrusted and must not run automatically. Scanning, quarantine, and incident recovery are not defined or proven.

BLUE must measure supported data and usable capacity before it claims protection. If there is not enough room, it should stop and explain what is needed. It must not quietly leave required files behind or approve GOLD based on a partial copy.

Do not use GOLD. Neither REVIEW nor STOP authorizes installation. Do not alter Windows or overwrite the last verified BLUE copy. BLUE may contain partial or failed work, so follow only the released recovery procedure and never count it as protected until it is verified again. If no procedure is provided, stop and wait for help. This behavior is not proven yet.

No customer procedure exists yet. A future released process must check that the computer is supported, BLUE has enough room, stable power is available, required accounts can be accessed again, and an independent backup and recovery path are in place. Any unresolved REVIEW or STOP result means do not start GOLD.

That is exactly what the product is meant to avoid. The normal journey should use plain choices such as save my stuff and bring my stuff back. Some computers may still require a short startup step, but it should be specific to that machine. Novice usability has not yet been proven in customer trials.

Probably for some downloads, account sign-ins, updates, and application setup, but the exact requirement is not final. The core copy between your computer and BLUE should remain local. Any required online step must be disclosed before the switch, not discovered halfway through it.

There is no honest universal estimate yet. Time will depend on how much data you have, the speed and health of the computer and BLUE device, downloads, installation, verification, and any exceptions. Qualification should provide a realistic estimate only after measuring the actual setup.

No customer migration-support channel, hours, response target, escalation route, or support entitlement exists today. Clear on-screen recovery instructions and an assisted option are being considered, but “assisted migration” on this page is only demand research. No helper should receive passwords, recovery keys, personal files, or unrestricted logs.

256 GB, 512 GB, 1 TB, and 2 TB are capacity candidates, not confirmed products or tiers. BLUE must have enough usable space for the files it promises to protect, with room for verification data and safe operation. Qualification should recommend a fit only after measuring your actual supported data.

A customer-supplied-drive or software-only path is being considered. It would need clear requirements because drive health, capacity, speed, formatting, encryption, and connection type all affect safety. Preparing that separate drive could erase what is already on it, so a released process must identify the drive, explain the consequence, and ask first. It is not yet a confirmed offer.

No recurring-fee model is selected, and subscriptions are outside the current proof. A future online, support, update, or backup service would need a separate offer, price, consent, data-flow explanation, and cancellation terms.

The leading idea is that you would keep BLUE. No ongoing or automatic backup is promised today. BLUE could later become a local backup device, but its schedule, versions, retention, capacity, recovery, deletion behavior, and safe disposal process are not defined. A migration copy is not a complete, off-site backup plan.

WELCOME is the optional onboarding step after restore. It could explain where files went, help with unfamiliar apps, and teach the new environment. A private local assistant is one future idea. It would be optional, would not be required for migration, and could never decide that your data is safe or authorize GOLD.

WELCOME should start with a privacy-safe migration summary, hardware details, app inventory, and unresolved items, not document contents, passwords, tokens, or private keys. Any later file access or cloud connection would need a separate, explicit choice and clear limits. Migration must work without AI, and AI can never approve BLUE or GOLD.

Compatibility cannot be assumed forever. A released kit would need to identify the exact Omarchy version and hardware it was qualified against. Material installer, firmware, driver, or operating-system changes must be checked again. An old READY TO SWITCH result must never be reused as proof that a newer setup is safe.

No customer update channel, schedule, supported lifetime, end-of-life policy, or included update entitlement exists today. Each exact BLUE, GOLD, hardware, and Omarchy release must be qualified. A stale READY result cannot authorize a changed release.

Not proven yet. The intended flow should support keyboard operation, readable text, visible focus, non-color status messages, and screen-reader announcements. Magnification, voice control, switch access, boot-time steps, and destination support still need testing. If a tool you depend on is unknown or unsupported, the process must say REVIEW or STOP.

The page includes keyboard-operated disclosures, visible focus, readable status text, and announced form states, with automated browser checks for key behavior. That is not a claim of full WCAG 2.2 AA or broad screen-reader, voice-control, or switch-access conformance. If this page blocks you, contact Intent Solutions through the Privacy Policy contact route.

No final product, tier, capacity, included service, or price exists. Every option and capacity on this page is a demand-research idea. Clear prices and inclusions must be published before anyone is asked to buy.

Shipping regions, carriers, delivery timing, taxes or duties, fulfillment methods, and release date are not set. Registering interest does not reserve inventory or a shipping position.

None is offered today because nothing is for sale. Warranty coverage, return windows, refund eligibility, replacement steps, costs, and failure recourse must be published before purchase. Do not infer future product terms from this site's general Terms.

You consent only to the listed BLUE GOLD BLUE research, interview, product-update, or future-pilot communications. It creates no order, reservation, eligibility decision, purchase obligation, service agreement, support entitlement, or permission to attempt the migration.

You submit your name, email, and optional product preferences. They are held server-side as an encrypted pending record and are not added to the confirmed interest list until you explicitly confirm within 48 hours. After confirmation, Intent Solutions may contact you only for the listed purposes. An exact expired-record retention period is not published yet. The form has no file upload and does not ask for passwords. Website analytics are described in the Privacy Policy; form answers are not intentionally sent as custom analytics events.

It is sent only after this form is submitted, uses the subject “Confirm your BLUE GOLD BLUE interest,” and links back to this page on oma.intentsolutions.io. The link contains a short opaque confirmation code, not your answers, and expires after 48 hours. Opening it does not confirm automatically. You must press the confirmation button on this page. If you did not request it, do not confirm.

Yes. You can unsubscribe from communications or request access, correction, or deletion through the contact route in the Privacy Policy. Limited suppression or legally required records may remain. Registration creates no order or reservation, so there is no purchase to cancel.