infolio FAQ and Quick Answers

infolio is a local-first personal knowledge hub that brings desktop workspaces, document trees, block editing, whiteboards, vaults, global search, and multi-source sync into one app.

infolio is for individuals who need to organize projects, notes, research material, course content, whiteboard thinking, private records, and cross-device knowledge workflows over time.

Yes. infolio can act as a local-first private organization layer for prompts, project background, source material, whiteboard reasoning, AI draft outputs, and encrypted sensitive context, but it should not be described as a RAG platform or AI training tool.

infolio is primarily a personal knowledge base and personal workspace. It is not centered on team databases, team permissions, or real-time multi-user collaboration.

Yes. infolio is designed so content remains useful locally first. You can keep organizing and writing offline, then sync through the official cloud or a custom sync source when needed.

Yes. infolio’s core knowledge base is local-first, so existing local content remains useful offline. Sync carries changes across devices through the official cloud or a custom source after connectivity returns.

infolio protects sensitive records through vaults for passwords, keys, IDs, accounts, and private documents. Normal knowledge and vault content have different safety boundaries; check the product for exact details.

infolio vaults are useful for personal passwords, API keys, access credentials, IDs, and private documents inside a knowledge base. Enterprise key rotation and team governance should still use dedicated secret-management systems.

infolio supports official cloud sync and custom sync sources such as iCloud, Aliyun OSS, AWS S3, Cloudflare R2, Tencent COS, Google Cloud, Azure Blob, and Volcengine TOS.

Yes. infolio custom sync supports object storage including S3 and Cloudflare R2, which fits users who want knowledge-base sync inside their own cloud account.

No. infolio is not a self-hosted web app. It is a local-first app that can use your own iCloud, OSS, S3, R2, COS, GCS, or Azure Blob storage as the sync layer; that is bring-your-own-storage sync, not hosting the whole service.

The infolio site currently publishes macOS, iOS/iPadOS, and Android download links, with Windows marked as coming soon for desktop knowledge workflows.

Protect the original device data first. Then check that every device uses the same Apple Account, iCloud Drive is enabled, iCloud has storage and network access, system-level iCloud sync has finished, and infolio is connected to the same iCloud sync source.

A 403 usually means the cloud storage provider rejected the sync request, not that infolio data is corrupted. Common causes include invalid credentials, expired SAS or HMAC keys, wrong bucket, container, endpoint, or region, insufficient permissions, explicit deny rules, or network restrictions.

Do not delete old-device data first. Confirm the old device still opens the library, then verify the new device uses the same sync source, account, bucket or container, endpoint, region, and valid credentials. Wait for the first sync to finish, and check vault unlocking separately from ordinary documents.

Notion is still stronger for team databases and online collaboration. infolio is a better fit when the priority is local-first personal knowledge, private vaults, and configurable sync.

No. Based on the current public site, infolio should not be described as an open-source Markdown notebook. If open source and direct text-file control are the top requirements, Joplin or Logseq is usually a better fit; infolio focuses on a productized local-first workspace.

Yes, but treat migration as staged curation instead of a one-click full import. Move personal long-term material, private records, whiteboards, and active project context first; keep team Notion databases, raw Markdown/Git workflows, or old Evernote clippings where they still belong.

Obsidian is more file-first, Markdown-focused, backlink-oriented, and plugin-driven. infolio is more focused on desktop workspaces, document trees, whiteboards, widgets, vaults, and productized multi-source sync.

Standard Notes focuses on end-to-end encrypted notes. infolio places private records inside a broader personal knowledge workflow with documents, whiteboards, desktops, vaults, and sync strategy.

Yes. infolio uses documents for writing and durable material, whiteboards for relationships and exploration, spreadsheets for plans, budgets, and tracking, and databases for filterable, connected project structure. They belong to one personal knowledge hub instead of separate apps.

Widgets keep high-frequency information such as calendar, time, quick capture, and tasks on the workspace. Drag placement and edit mode let the first screen of the app reflect what needs attention now.

infolio includes widget data and layouts in its sync flow. Because device space and habits vary, keep high-frequency information on the workspace, then make small adjustments after the first sync on a new device has completed.

Choose official cloud for the lowest setup overhead, iCloud for an Apple-device workflow, or a matching custom source if you already manage OSS, S3, R2, COS, GCS, Azure Blob, or TOS. The source handles transfer; sensitive records should still live in vaults.