Skip to main content

Overview

Bowrain holds the context graph for every project in a workspace: the profiles, the terms, the content memory and the decisions people make about them. The Bowrain server keeps all of it in one place. You reach the workspace through a browser or the native desktop app. Both are real-time clients with the same hub, review session, editor, presence and history. Developers reach the same workspace through server runs. Items a run holds back arrive in review, and your approvals feed the next run.

Client-specific differences are noted inline. The desktop app page covers what is different about the native client.

A quick tour​

These short tours run against a live workspace.

The Context hub​

The hub opens on one profile card for each point where the workspace's content sits. A card shows the voice profile that applies, the terms in force, what the checks report, what is waiting in review, and who holds the point. Terms are concepts with relations, per-market validity and a history. A far-reaching change goes through a change-set, and Bowrain measures its blast radius before anyone approves it. See Context.

Outdated wording

The narration uses terminology that has since been retired. The interface and the behaviour shown are unchanged.

Review​

A run drafts and checks content, and holds back for review what a machine cannot decide. The review session lists every pending block across items and locales, with the source, the draft, the checks and the voice findings side by side. A reviewer approves, rejects or edits each block, or corrects the context itself. The last approval starts the run that delivers the results. See Review.

Checks that learn from corrections​

Bowrain groups the phrasings people keep fixing into candidate rules. For each candidate it shows the blast radius across real content, and when a reviewer approves it, the candidate becomes an enforced check. The check applies to everyone in the workspace and to every connected AI tool. See Voice and corrections.

The editor​

The editor shows a file's source and target side by side, with a live preview of the page. Beside each block are the matches from the workspace content memory and the terms in force at its point. You edit the source and every target locale in the same editor. See The editor.

Outdated wording

The narration uses terminology that has since been retired. The interface and the behaviour shown are unchanged.

Collaboration and streams​

You invite teammates to a workspace by email and give each one a role, bound to a language or a point where that fits. Streams keep parallel work apart. Like a branch, a stream holds a rebrand or a risky pass until you compare it and merge it back into the main line. See Real-time collaboration.

Outdated wording

The narration uses terminology that has since been retired. The interface and the behaviour shown are unchanged.

The main screens​

Workspace home​

The workspace rail on the left switches between workspaces. Each workspace is an isolated environment with its own projects, profiles, terms and content memory. The home page lists the active workspace's projects, each with its name, source language, any target languages and file count.

Workspace home with the workspace rail and project listWorkspace home with the workspace rail and project list

A project's Map​

A project opens on its Map: counts of files, blocks, rules and findings, the suggestions waiting for a decision, and one row per file. Upload files by dragging them onto the project's Overview, or click Add Files.

A project on its Map, with counts, open suggestions and the file listA project on its Map, with counts, open suggestions and the file list

Other screens have their own pages:

ScreenWhat it showsPage
Sign-inThe identity provider's sign-inFirst login
ConceptsConcepts beside a detail paneTerms
Content memoryApproved pairs beside a detail paneContent memory
ReviewThe session and the inboxReview
SettingsWorkspace name, slug, description and your roleWorkspaces

What the workspace holds​

  • The context graph: profiles per point, concepts with relations and per-market validity, voice profiles, change-sets with blast radius and pilots, and the decisions people made about them. See Context.
  • Review: one session per project, a workspace inbox, ship states per locale, and review in place. See Review.
  • An editor with Visual and Table views, inline tag support, and per-block memory and term context, for the source and for every target locale.
  • Content memory with tiered matching and governed version reuse.
  • AI drafting on the workspace's credits or on your own provider key, with any provider the engine's translate tool supports.
  • Every format the engine reads and writes, listed in the format reference.
  • Workspaces with role-based access, grants bound to a language or a point, and single sign-on through an identity provider.

Deployment​

The platform is served by bowrain-server. Users authenticate through an identity provider and can belong to multiple workspaces with different roles. See Self-hosting for deployment instructions.

Browser and desktop clients​

The browser and the desktop app share the same surfaces and connect to the same server and workspaces, so presence, sign-on, the hub, review and the content memory are shared across them. The desktop client adds offline editing and runs as a native app. See The desktop app for the full comparison.