Beta limitations

AuroraDocs is in public beta. The product is free while it is in beta, and there are no paid plans during the beta period. Signup on production is open; staging remains invite-gated for preview builds.

This page lists the limitations we want you to know before you rely on AuroraDocs for something important. It is the honesty companion to the Beta label on the marketing site and in the app.

What beta means

• Free while beta — no paid Plus/Pro checkout during beta. We give at least 30 days' notice before any paid plan launches (see Terms).
• Labeled, not invite-walled — you can create a free account or try the browser app without one. Known limits are disclosed here rather than hidden behind a waitlist.
• Production baseline — announcements should match what is live on production, not features that exist only on staging or unreleased main builds.

Encryption scope

End-to-end encryption (E2EE) covers the main object content body, titles, property values, comments, workspace chat messages, and uploaded file/image bytes when E2EE is active.

It does not cover every piece of structural or operational metadata the service needs to sync and operate (for example some routing, membership, and sync-control fields). Treat E2EE as strong protection for your content and attachments — not as “the entire workspace is invisible to the server.”

See Security & encryption and the Privacy Policy for the current wording.

Desktop platforms

The desktop app targets macOS, Windows, and Linux in principle. During public beta, the stable publish feed prioritizes Apple Silicon macOS (darwin-aarch64). Other architectures may be paused or incomplete until the matrix is restored and QA'd.

Prefer the web app or check the download page for what the live feed actually offers. Details: Desktop app.

Speech and hosted AI

• Hosted speech-to-text and text-to-speech on the AuroraAI custom gateway fail closed under the current hosted-chat policy. Do not expect built-in hosted STT/TTS to work until that path is explicitly re-enabled and signed off.
• Bring-your-own-key (BYOK) speech providers can send audio from your device to the provider you configure. That is a separate path from hosted AuroraAI speech.
• Hosted chat may already be available depending on deployment configuration; that does not imply hosted-AI legal sign-off is complete for every AI surface.

Do not treat speech as a marketed beta headline until live microphone and provider acceptance is done.

Sync forks

Sync conflicts are uncommon in normal use. In rare fork cases you may need Settings → Sync and a rebase/resolution step rather than an automatic silent merge. Prefer resolving forks deliberately over force-overwriting another device.

Mobile and companion apps

Phone/tablet and companion-app surfaces (including Apple TestFlight / native Sign in with Apple ops) still have incomplete device gates. Mobile has its own known limitations. Do not assume desktop or web parity on every phone workflow yet.

Soft / deferred gates (disclosed, not blockers for free beta)

These remain open product or ops decisions; they do not block calling the free AuroraCloud product a public beta, but they must not be announced as finished:

• Further E2EE product decisions (fork-resolution UX polish, rotation step-up). Enforced-write checkpoint mode is scheduled for 2026-10-15 UTC (web/desktop min 0.11.5; mobile dual-write must land first or operators delay via env). Sync-tier resolution now fails closed to offline when storage is unreadable.
• Calendar OAuth production configuration and real-provider QA.
• Full multi-platform desktop matrix restore.
• Paid plans / Stripe activation and hosted-AI vendor DPA sign-off (blocked by design for paid / full AI launch; not required for free beta).

Support

Email contact@auroradocs.eu for beta support, abuse/takedown, and privacy requests. Abuse contacts are also linked from the Terms.