NeuralScio keeps local desktop state as the base layer for saved papers, cached reading, annotations, and local configuration. Sync surfaces may be exposed in some Public Alpha builds, but they are not tied to active Pro/Team billing.
What Sync Is For
Use sync when your current build or account configuration exposes it and you want:
- account-linked continuity across signed-in devices
- cloud continuity on top of the local desktop workflow
- future billing or entitlement state when those systems launch
What Stays Local
Several local-first surfaces stay on the machine:
- local PDF library
- cached PDFs and cached web content
- local annotations and reading state
- local AI workflows through the built-in worker or the Ollama-compatible provider
- local MCP stdio workflows on the same machine
Practical Boundary
- sync availability depends on the current alpha build and account configuration
- local storage remains the foundation
- provider search and cloud AI still require network access
- large local artifacts may need to be re-cached or re-imported on another machine
When To Use Sync
- when you want the same account context on more than one device
- when your current build exposes the sync flow for testing
- when you want cloud continuity on top of the local desktop workflow
Limits
Sync is not the only copy of your research data. NeuralScio is a desktop application with meaningful local state, local caches, and local AI options.