Known limits

The gaps most likely to affect you, written down deliberately rather than discovered.

Reference Updated 2026-09-24

Every product has these. Most do not write them down. This page exists so you can decide with the real picture rather than finding out during a sprint.

Reliability

It is an early product. Bugs, interruptions, storage failures and data loss remain possible. Keep independent copies of anything you cannot afford to lose.

No uptime target and no tested restore path. Backup configuration and retention need deployment-specific confirmation; no supported recovery commitment is established here. See Privacy and your data.

Browser storage can be lost. Orneos requests persistent storage at startup when supported, but the browser can deny the request. Eviction when persistence is not granted, manual deletion, private-session cleanup and storage failures can destroy unsent work. See Local data and storage.

Offline

An offline refresh or cold start may not load the app. The cached application shell is not yet verified for every document navigation. Local data and queued changes are separate from loading that shell; a failed offline page load does not itself erase them. Reconnect to regain access, and do not clear storage as a repair.

Vault is not offline-capable. Page content is not stored locally, so reading a page needs a connection and a refresh while offline loses what you were looking at. This is the largest gap between what the platform does for issues and what it does for documents. Planned.

Failed changes need attention. The worker attempts queued changes across member teams, but rejected or failed changes are not proof of server acceptance. Check their status before clearing storage or signing out. See Offline and reconnect.

Signing out destroys unsent work. By design; a principal boundary has to destroy the replica. Let the queue drain first.

Scale

The multi-team background fill is unbounded. Orneos keeps every team you belong to converging in the background. There is no published, measured supported team-count limit. More teams can mean more local storage and background traffic; discuss your expected scale before relying on it.

Replay history is limited. If your client is behind by more than the server’s retained window, it rebuilds from scratch instead of replaying. Correct, and occasionally slow after a long absence.

Single region. No multi-region replication. Latency reflects distance from the hosting region; the local-first architecture hides most of it for your own edits but not for a colleague’s changes reaching you.

Product gaps

No notifications. @mentions mark a comment but do not reach anyone who is not looking. This surprises people, so it is worth stating twice.

No supported tracker integrations. No Slack or GitHub synchronization, self-service board importer or customer webhooks. AI-provider connections are separate; see Integrations.

No public API. Two read-only MCP tools, Work in progress and not enabled by this docs release. The internal GraphQL endpoint is not a supported public integration contract.

Search has local and online paths. Spotlight and Team issue search use the active team; the Search page defaults to online Company scope for authorized cross-team issues. Company queries and Vault full-text body search require a connection. Search views can be saved; comments are not a complete searchable archive and text query operators are not implemented. See Search and Spotlight.

No agent execution. Nothing in Orneos does work on your behalf. See Agent execution.

No customer-facing audit log, SSO or SCIM.

Review workflow

The complete review surface is not released. Context delivery, capture and review are work in progress. Automatic bundles already assemble available Orneos context; assisted early access bridges external intake and evidence interpretation. See what still needs automation.

Gaps to consider

When evaluating fit, consider these gaps:

  1. Vault offline — documents do not yet have the offline behavior of local issue data.
  2. Bounded multi-team working set — limiting storage and background traffic as memberships grow. Persistent-storage requests already exist, but their grant is browser-controlled.
  3. Notifications — mentions do not deliver a notification today.

If your blocker is something else, tell us. Your workflow helps determine which limitation matters most.

Something here wrong, missing or out of date? Tell us at support@orneos.com — corrections to these pages are welcome and we would rather hear it than have you work around it.