CORENEXT ATLAS
Free-use license
Application-specific terms for the 1.0.1 Official Preview.
Free to use
You may download, install, and use this release without charge for personal or business purposes on computers you own or are authorized to administer. This is not an open-source license and does not permit selling, rebranding, or redistributing modified copies.
The preview is provided as available without guaranteed compatibility, recovery, uninterrupted operation, or response time. Mandatory rights that cannot lawfully be excluded remain unaffected.
Full release license and notices
CORENEXT ATLAS 1.0 — OFFICIAL PREVIEW
by CoreNextStudio · Free to use
CoreNextStudio is the brand of an individual developer in Alaska, United States, not a representation of incorporation. Contact: contact@corenextstudio.com. Support: https://corenextstudio.com/contact/.
FREE-USE LICENSE
You may download, install and use this release at no charge for personal or business purposes on computers you own or are authorized to administer. Keep backup copies. This is not a transfer of ownership or an open-source license. It does not grant permission to sell Atlas, redistribute third-party packages, or use the brand to imply endorsement. Applicable mandatory rights remain unaffected. Third-party tools, Windows and vendor downloads retain their own licenses. Windows activation rights are not included.
PREVIEW LIMITS
Atlas file snapshots and Windows system images are separate workflows. For Atlas file snapshots: File contents and last-write times are backed up. Windows ACLs, alternate data streams, EFS keys, app registrations, registry settings and operating-system boot state are not preserved. Linked folders and cloud placeholders are excluded with recorded warnings. EFS-encrypted files stop the snapshot. Inaccessible files stop the operation rather than silently creating a successful snapshot. Close applications first; this is not a VSS or application-consistent snapshot.
Restore verifies objects before writing and creates a new destination folder. Incomplete operations can leave partial output or unreferenced backup objects; keep original data. Verify the backup and test restoring representative files before erasing Windows. A checksum verifies consistency against the manifest, not the trustworthiness of a publisher or the health of original content. Use a different physical device for disaster protection.
Encrypted vaults use AES-256-CBC with HMAC-SHA256 authentication and PBKDF2-HMAC-SHA256 (200,000 iterations). Contents and snapshot metadata are encrypted; object names expose content hashes and the filesystem exposes object sizes/counts and snapshot timestamps. Interactive passwords are not saved. An encrypted daily schedule can save its vault password under Windows DPAPI only after explicit consent; there is no recovery service. Encryption implementation has fixture tests, not an independent security audit. Keep your password separately. The app cannot recover a forgotten password.
WINDOWS AND USB TOOLS
Atlas can write Windows x64 UEFI installation USB media from a local ISO after an erase review, typed confirmation and Windows administrator permission. The selected USB is erased and formatted as GPT/FAT32 (up to 30 GB). Disk identity, Windows disk, source ISO, running app and known vault locations are checked. Large install.wim files are split with DISM; other copied files are compared by SHA-256. These checks do not prove bootability or authenticate the whole ISO. Optional booted-Setup TPM/Secure Boot/RAM overrides are experimental, not in-place-upgrade bypasses or firmware security changes. Unsupported Windows installations may not receive updates; missing CPU capabilities cannot be added by a workaround. No arbitrary downgrade preserves all apps/settings.
System images use Windows wbadmin with allCritical and vssCopy on an eligible external NTFS volume. Windows controls image contents, consistency, space and retention. A completed command is not proof of successful recovery. Windows RecoveryDrive or installation media supplies the recovery environment; Atlas does not provide its own WinPE image. USB boot, image recovery and installation require further hardware validation. Media operations may continue until completion even when other Atlas jobs support cancellation.
PRIVACY AND STORAGE
Selected file paths and contents are read locally and saved only to the vault/destination you choose. Source paths, relative names, file lengths, times, checksums and exclusions form each snapshot. Snapshot history is kept without automatic pruning. Incremental backups reuse identical objects; move the whole vault, not individual snapshot files. Local sync clients and network servers receive files when chosen as destinations; Atlas cannot verify sync completion. The direct HTTPS WebDAV workflow transmits stored vault files and an Authorization header to the server you select. Plain vaults remain readable to that server; encrypted vaults retain their encryption but expose sizes, object hashes and snapshot timestamps. Uploads read back files for verification and publish snapshot metadata last. Downloaded objects are verified before the local snapshot is committed. Failed transfers may leave partial remote objects or local pending files. No remote deletion is performed. WebDAV credentials remain in memory and are cleared from the UI after successful transfer; they are not persisted. TLS certificate validation and same-origin path restrictions are enforced. Server logging, retention and account handling remain governed by your provider.
Direct Dropbox, Google Drive, and OneDrive connections use the provider's browser sign-in screen. Dropbox and OneDrive access is limited to the Atlas app folder; Google uses drive.file access to files created by Atlas or explicitly shared with it. The connection token is protected with Windows DPAPI for the current Windows account and saved on this PC. Disconnect removes that saved connection; you can also revoke access in your provider's connected-app settings. Passwords for your provider account are not entered into Atlas. Backup encryption passwords are not sent to the provider. Uploads send a complete vault in verified chunks and a completion record including the computer name, backup date, encrypted status, size and checksums. Encryption protects vault contents, but these transfer details and file sizes remain visible. Unencrypted backups are readable by the storage provider. Temporary local space and a local vault are required. Files are downloaded to a new folder and verified before being offered for restore. Interrupted transfers may leave incomplete cloud parts or local pending files. Cloud storage limits, retention and account handling are controlled by the provider. Cloud sign-in is separate from app update checks. Scheduled backups currently save locally; they do not automatically upload to cloud accounts.
Appearance, completion-message preference and last backup folder are saved under LocalAppData/CoreNextStudio/Atlas/settings.json. Portable mode uses this location too. Passwords and selected-source lists are not persisted there. Close Atlas before deleting settings to reset them. Activity is kept in memory unless you export it and may contain paths or error details. The inventory export includes Windows, hardware and registry-listed desktop apps; it omits product keys and credentials. Exported reports and vaults remain until you remove them. Uninstalling keeps them and local preferences; it removes the Atlas scheduled task and saved schedule plan/password.
No Atlas account service, telemetry, advertising or automatic crash upload is implemented. A build without a valid publisher signature makes no automatic update-feed request. A signed release contacts the CoreNextStudio website only when the user checks manually or enables automatic checks. Clicking official web links opens your browser. Downloaded tool signature validation may contact certificate services according to Windows policy. These parties can receive ordinary network metadata under their own policies.
SCHEDULE PRIVACY
A reviewed daily schedule stores selected source paths, the vault path, its configuration fingerprint and local time in LocalAppData/CoreNextStudio/Atlas/schedule.json. If expressly allowed for an encrypted vault, it also stores a DPAPI-protected password. Programs running as your Windows user may be able to decrypt it. No Windows login password is stored. Windows Task Scheduler launches the current Atlas executable while you are signed in; it does not wake the PC and only starts on AC power. Missed runs can start when conditions permit. The last scheduled result and exclusion paths are stored in schedule-result.txt. Media-operation reports are also saved in the Atlas local app-data folder. Remove schedule stops future runs, not necessarily a run already active. Removing the task/plan does not delete backups or previously saved result reports.
Support messages are voluntary. The website privacy policy at https://corenextstudio.com/privacy-policy/ describes submitted information, support uses, service providers, retention and privacy requests. Messages may be kept while needed to answer the request, maintain reasonable support and security records, resolve disputes or meet legal obligations; there is no fixed automatic deletion schedule. You may request deletion of information that does not need to be retained for legal, security or operational reasons. Send only necessary details, never passwords, encryption keys or unrelated personal files.
The preview is provided as available without guaranteed recovery, uninterrupted operation, performance or response time. To the extent allowed by law, implied warranties of merchantability and fitness for a particular purpose are disclaimed. Mandatory consumer rights and liability that cannot lawfully be excluded remain unaffected. No Microsoft, Rufus or other vendor endorsement is claimed. Standard Windows 10 support has ended; intended OS compatibility does not extend Microsoft's support lifecycle. Windows 11 x64 is the development host. Windows 10, ARM64 and other hardware still require validation.
by CoreNextStudio · Free to use
CoreNextStudio is the brand of an individual developer in Alaska, United States, not a representation of incorporation. Contact: contact@corenextstudio.com. Support: https://corenextstudio.com/contact/.
FREE-USE LICENSE
You may download, install and use this release at no charge for personal or business purposes on computers you own or are authorized to administer. Keep backup copies. This is not a transfer of ownership or an open-source license. It does not grant permission to sell Atlas, redistribute third-party packages, or use the brand to imply endorsement. Applicable mandatory rights remain unaffected. Third-party tools, Windows and vendor downloads retain their own licenses. Windows activation rights are not included.
PREVIEW LIMITS
Atlas file snapshots and Windows system images are separate workflows. For Atlas file snapshots: File contents and last-write times are backed up. Windows ACLs, alternate data streams, EFS keys, app registrations, registry settings and operating-system boot state are not preserved. Linked folders and cloud placeholders are excluded with recorded warnings. EFS-encrypted files stop the snapshot. Inaccessible files stop the operation rather than silently creating a successful snapshot. Close applications first; this is not a VSS or application-consistent snapshot.
Restore verifies objects before writing and creates a new destination folder. Incomplete operations can leave partial output or unreferenced backup objects; keep original data. Verify the backup and test restoring representative files before erasing Windows. A checksum verifies consistency against the manifest, not the trustworthiness of a publisher or the health of original content. Use a different physical device for disaster protection.
Encrypted vaults use AES-256-CBC with HMAC-SHA256 authentication and PBKDF2-HMAC-SHA256 (200,000 iterations). Contents and snapshot metadata are encrypted; object names expose content hashes and the filesystem exposes object sizes/counts and snapshot timestamps. Interactive passwords are not saved. An encrypted daily schedule can save its vault password under Windows DPAPI only after explicit consent; there is no recovery service. Encryption implementation has fixture tests, not an independent security audit. Keep your password separately. The app cannot recover a forgotten password.
WINDOWS AND USB TOOLS
Atlas can write Windows x64 UEFI installation USB media from a local ISO after an erase review, typed confirmation and Windows administrator permission. The selected USB is erased and formatted as GPT/FAT32 (up to 30 GB). Disk identity, Windows disk, source ISO, running app and known vault locations are checked. Large install.wim files are split with DISM; other copied files are compared by SHA-256. These checks do not prove bootability or authenticate the whole ISO. Optional booted-Setup TPM/Secure Boot/RAM overrides are experimental, not in-place-upgrade bypasses or firmware security changes. Unsupported Windows installations may not receive updates; missing CPU capabilities cannot be added by a workaround. No arbitrary downgrade preserves all apps/settings.
System images use Windows wbadmin with allCritical and vssCopy on an eligible external NTFS volume. Windows controls image contents, consistency, space and retention. A completed command is not proof of successful recovery. Windows RecoveryDrive or installation media supplies the recovery environment; Atlas does not provide its own WinPE image. USB boot, image recovery and installation require further hardware validation. Media operations may continue until completion even when other Atlas jobs support cancellation.
PRIVACY AND STORAGE
Selected file paths and contents are read locally and saved only to the vault/destination you choose. Source paths, relative names, file lengths, times, checksums and exclusions form each snapshot. Snapshot history is kept without automatic pruning. Incremental backups reuse identical objects; move the whole vault, not individual snapshot files. Local sync clients and network servers receive files when chosen as destinations; Atlas cannot verify sync completion. The direct HTTPS WebDAV workflow transmits stored vault files and an Authorization header to the server you select. Plain vaults remain readable to that server; encrypted vaults retain their encryption but expose sizes, object hashes and snapshot timestamps. Uploads read back files for verification and publish snapshot metadata last. Downloaded objects are verified before the local snapshot is committed. Failed transfers may leave partial remote objects or local pending files. No remote deletion is performed. WebDAV credentials remain in memory and are cleared from the UI after successful transfer; they are not persisted. TLS certificate validation and same-origin path restrictions are enforced. Server logging, retention and account handling remain governed by your provider.
Direct Dropbox, Google Drive, and OneDrive connections use the provider's browser sign-in screen. Dropbox and OneDrive access is limited to the Atlas app folder; Google uses drive.file access to files created by Atlas or explicitly shared with it. The connection token is protected with Windows DPAPI for the current Windows account and saved on this PC. Disconnect removes that saved connection; you can also revoke access in your provider's connected-app settings. Passwords for your provider account are not entered into Atlas. Backup encryption passwords are not sent to the provider. Uploads send a complete vault in verified chunks and a completion record including the computer name, backup date, encrypted status, size and checksums. Encryption protects vault contents, but these transfer details and file sizes remain visible. Unencrypted backups are readable by the storage provider. Temporary local space and a local vault are required. Files are downloaded to a new folder and verified before being offered for restore. Interrupted transfers may leave incomplete cloud parts or local pending files. Cloud storage limits, retention and account handling are controlled by the provider. Cloud sign-in is separate from app update checks. Scheduled backups currently save locally; they do not automatically upload to cloud accounts.
Appearance, completion-message preference and last backup folder are saved under LocalAppData/CoreNextStudio/Atlas/settings.json. Portable mode uses this location too. Passwords and selected-source lists are not persisted there. Close Atlas before deleting settings to reset them. Activity is kept in memory unless you export it and may contain paths or error details. The inventory export includes Windows, hardware and registry-listed desktop apps; it omits product keys and credentials. Exported reports and vaults remain until you remove them. Uninstalling keeps them and local preferences; it removes the Atlas scheduled task and saved schedule plan/password.
No Atlas account service, telemetry, advertising or automatic crash upload is implemented. A build without a valid publisher signature makes no automatic update-feed request. A signed release contacts the CoreNextStudio website only when the user checks manually or enables automatic checks. Clicking official web links opens your browser. Downloaded tool signature validation may contact certificate services according to Windows policy. These parties can receive ordinary network metadata under their own policies.
SCHEDULE PRIVACY
A reviewed daily schedule stores selected source paths, the vault path, its configuration fingerprint and local time in LocalAppData/CoreNextStudio/Atlas/schedule.json. If expressly allowed for an encrypted vault, it also stores a DPAPI-protected password. Programs running as your Windows user may be able to decrypt it. No Windows login password is stored. Windows Task Scheduler launches the current Atlas executable while you are signed in; it does not wake the PC and only starts on AC power. Missed runs can start when conditions permit. The last scheduled result and exclusion paths are stored in schedule-result.txt. Media-operation reports are also saved in the Atlas local app-data folder. Remove schedule stops future runs, not necessarily a run already active. Removing the task/plan does not delete backups or previously saved result reports.
Support messages are voluntary. The website privacy policy at https://corenextstudio.com/privacy-policy/ describes submitted information, support uses, service providers, retention and privacy requests. Messages may be kept while needed to answer the request, maintain reasonable support and security records, resolve disputes or meet legal obligations; there is no fixed automatic deletion schedule. You may request deletion of information that does not need to be retained for legal, security or operational reasons. Send only necessary details, never passwords, encryption keys or unrelated personal files.
The preview is provided as available without guaranteed recovery, uninterrupted operation, performance or response time. To the extent allowed by law, implied warranties of merchantability and fitness for a particular purpose are disclaimed. Mandatory consumer rights and liability that cannot lawfully be excluded remain unaffected. No Microsoft, Rufus or other vendor endorsement is claimed. Standard Windows 10 support has ended; intended OS compatibility does not extend Microsoft's support lifecycle. Windows 11 x64 is the development host. Windows 10, ARM64 and other hardware still require validation.
Operator and contact
DriverForge and CoreNext Atlas are developed and operated independently by George Papadakis under the CoreNextStudio publishing name in Alaska, United States.
Support and privacy requests · Website Privacy Policy · Checksums
This web summary does not replace the full notice included with the application download.