Quasar product guideQuasar product guide · Rev. 2 ·

Quasar product guide

What Quasar does not do

The limits of Quasar 2026.10.15, stated plainly, so nobody discovers them after buying. Covered: - interface: English only, desktop only; - search: full-text within one project, no semantic or AI search; - git: Quasar never writes to repositories, never runs git commands and never guesses versions; - integrations: no outbound webhooks, no chat integrations, MCP authenticates with API keys only; - documents: no WYSIWYG editor, published releases are permanent, export format limits; - planning: no per-person capacity; - security: no SMS codes, antivirus off unless configured, no in-app restore of backups; - public guides: images not shown yet, no self-service custom domains. Read this before recommending Quasar for a specific need.

The limits of Quasar 2026.10.15. Some are deliberate choices; others are gaps that may close in a later version, and each says which.

Interface

  • English only, for now. The application's own words are in English. The interface was designed to be translated, and languages are the next step on the roadmap, starting with Italian and French. Documents can already be written in any language, and built-in document templates exist in English and Italian. A gap.
  • Desktop only. The interface is designed for screens 1,024 pixels wide and more. There is no mobile layout and no mobile app. A gap.
  • Accessibility.
    • Quasar targets WCAG 2.2 level AA. Colour is never the only signal, contrast is checked in both themes, and the Gantt chart has an equivalent table.
    • It does not meet the Reflow criterion (1.4.10), because of the desktop-only layout.
    • It has not yet been tested by a screen-reader user.

Search

  • Full-text, not semantic. Search matches words as written, with phrases, or and exclusions. There is no fuzzy matching, no "did you mean", and no AI or vector search. Deliberate: where meaning matters, an agent reads summaries and picks what is relevant, which works across languages.
  • One project at a time. Search covers the current project, not its sub-projects and not the whole organization. A gap.

Git and code

  • Quasar never writes to a repository. It observes branches, commits, tags and pipelines. It never creates a branch or a tag, merges, or commits. Its one write is the webhook that notifies it of new commits. Deliberate.
  • It never runs git commands for you. In the version flow it proposes the exact commands and checks afterwards that they happened.
  • It never guesses.
    • A version is never inferred from a branch name.
    • An issue is linked to a commit only when the commit's subject carries the issue key.
  • One repository per project.

Integrations

  • No outbound webhooks. Quasar does not call other systems when something changes. Agents and scripts use the REST API or MCP instead. A gap.
  • No chat integrations (Slack, Teams and the like). A gap.
  • MCP authenticates with API keys only. Agents connect with a personal key or a service-account key; there is no browser sign-in flow for MCP clients. Deliberate: it was built and removed because no client used it.
  • Email is used sparingly. Deadline reminders and password resets only; there are no notification digests by email.

Documents and releases

  • Markdown, not WYSIWYG. Documents are written as Markdown text and shown rendered; there is no visual editor.
  • Published releases are permanent.
    • A published revision cannot be unpublished or edited; you revise it into a new draft.
    • Uploaded artifacts cannot be replaced, and a withdrawal cannot be undone.
  • Export limits.
    • The PDF has no page numbers in its table of contents.
    • The PDF shows PNG and JPEG images, and Word also shows GIF.
    • Chinese, Japanese and Korean text does not print in the PDF.
    • The Markdown export carries no library images.
    • Quotes export as HTML.
  • No image generation. The asset library does not render icon sizes from a vector master. You upload each file.

Planning

  • No per-person capacity. Sprint workload compares each person with an even share of the sprint's capacity. There is no individual availability or holiday calendar per person; holidays are per organization or project. A gap.
  • Proposals, never automatic changes. Suggested sprint end dates and first work-log figures are proposals a person accepts.

Security and operations

  • No SMS codes. The second factor is an authenticator app or a security key. Deliberate.
  • API keys carry no second factor. When an organization requires two-factor authentication, the keys of a member who has not enrolled stop working.
  • Antivirus is off unless configured. Quasar supports ClamAV, and files above the scanner's limit are marked not scanned. A new installation has no scanner until one is configured.
  • Backups. Taken and kept by the operator of the installation. There is no restore button in the application.

Public guides

  • Images are not shown yet. Public pages of a published release render text only; serving a release's images publicly is planned. Quasar's own product guide carries no images in this version.
  • No self-service custom domains. The operator of an installation can map a host name to a guide, but an organization cannot attach its own domain by itself. Deliberate: certificates and domain verification are a product of their own.
  • One public release per publication. An organization can publish several releases, each under its own address.