Private by architecture.
Protected file contents, filenames, recovered versions, and version history are not intentionally uploaded to a Local Core service in the current beta.
Windows Early Access · 0.9.0-beta.1
Your file history.
On your computer.
Local Core quietly keeps recoverable versions of the folders you choose — locally, without uploading protected file contents to a Local Core service.
Local-first
Native watcher
Reversible restore
No product telemetry in beta.1
Protection status
Everything is protected.
Protected folders3Active
Recovery points248Local only
Last activityNowNative event
Recent historyView all
proposal.docxDocuments · 2 versions
launch-plan.pdfWork · 4 versions
budget.xlsxProjects · 7 versions
History without the cloud.
Native filesystem events capture changes while compressed, deduplicated recovery data stays in Local Core's local application storage.
Built for recovery.
Browse retained versions and restore regular file contents, with safeguards designed to preserve the file being replaced when possible.
How it works
Choose a folder.
Local Core handles the history.
No sync folder. No manual snapshots. Protect ordinary folders already on your PC and keep working as usual.
Select what matters.
Add the folders you want Local Core to protect. Missing or unavailable roots are handled conservatively rather than treated as mass deletions.
Keep working normally.
A native filesystem watcher observes changes. Local Core stores deduplicated recovery points locally according to retention, quota, and Safety Reserve policies.
↶
Go back when needed.
Preview retained history and restore a previous regular-file version. Local Core attempts a recovery point of the current file before replacing it.
Local-first privacy
Your files are the product.
Not the data source.
Local Core's Time Engine works on-device. The beta does not require a cloud service for monitoring, history, preview, or restore and does not include product telemetry or analytics reporting.
Read the Privacy Notice →Protected file contentsStay local
Version historyStay local
Product telemetryNot included in beta.1
Cloud account requiredNo
Local store encryption by Local CoreNot currently provided
Safety Reserve
Free-space protection takes priority.
Local Core keeps quota and Safety Reserve separate. When free disk space is under pressure, the reserve wins.
Default reserve: max(20 GB, 10% of disk capacity)
Unavailable folders
A missing drive is not a deleted folder.
Unavailable or unreadable protected roots are isolated so healthy roots can continue, while Local Core avoids inferring false file deletions.
DocumentsProtected
External SSDUnavailable
Early Access
Windows beta is next.
Local Core 0.9.0-beta.1 is being prepared for its first external Windows x64 testers. The installer will be unsigned and published only after the release checks, third-party notice review, clean-source build, lifecycle smoke test, and SHA-256 verification are complete.
Before installing: This is pre-release software and must not be your only backup. Windows may show an unknown-publisher or reputation warning because beta.1 is intentionally unsigned.
FAQ
Does Local Core upload my protected files?
No. The current Time Engine does not intentionally upload protected file contents, recovered versions, filenames, or version history to a Local Core service.
Is Early Access free?
Yes. The first Windows Early Access beta is free for evaluation and testing under the published Beta Terms.
Why is the Windows beta unsigned?
We are validating product interest and real-world behavior before paying for production signing infrastructure. The exact installer SHA-256 will be published when download opens.
Is Local Core a replacement for a backup?
No. During beta, keep an independent backup strategy appropriate to the importance of your data.