Branding
Who can do this: platform admins. Everyone in the organisation sees the result, and parts of it also show on the sign-in page before anyone signs in.1
Open Branding
Open Settings, then Branding.
2
Change the fields you need
Every field says where it shows. The Preview beside the form shows the left rail as your people will see it, and follows every keystroke.
3
Save
Click Save. The page confirms “Saved. Changes visible after reload.” Reload the page to see the change across Ainomos.
Identity
The setup instructions that AI apps follow name the Ainomos connection after the App name and the Environment, for example “Brain-DEV”. This keeps two Ainomos workspaces apart on one computer.
Colour & Theme
Start from a preset under Quick start: Red, Blue, Green (the default) or Grey. Then adjust any colour with its colour picker or a hex value such as #0a84ff.
Ainomos works out lighter, darker and text-on-brand variants of your primary colour automatically. To set them yourself, open Advanced variants: Primary light, Primary dark, Text on primary and Text strong.
In the contrast check, Ainomos checks each text colour against its background, including on a dark screen, and marks any pair that falls below the level. A warning does not stop you from saving. It tells you that some people may struggle to read that text.
Switch the preview between Light and Dark to check both. On a dark screen, Ainomos lifts your brand colour if it would disappear. Reset colours to default returns all colours to the default theme.
Logos
Click Choose file to upload. Ainomos accepts SVG, PNG, JPEG and WebP files up to 200 KB.
Sign-in page
Tick Show this workspace on the sign-in page to show your departments and teams, your chat models and the date your workspace started to anyone who opens your address. Project rooms are never shown. Leave it unticked to show only your branding.Footer
Undo changes
Most fields have a Reset to default button that clears your value and brings back the default. Reset everything to default at the foot of the preview does this for every field at once.Content language
Content language decides the language of new content that Ainomos writes with a model: decision drafts, dreaming proposals, rationales and summaries. You can choose German or English. It does not change:- The interface language. Each person chooses that for themselves in the Account menu, under Switch language.
- Existing content. Documents, decisions and drafts that already exist stay in the language they were written in.
- Chat answers. An answer follows the language of the question.
1
Open Content language
Open Settings, then Content language. The page shows the current value, for example “Currently: English”.
2
Choose the language
Click German or English. Ainomos saves at once and confirms “Saved.” The change is recorded as evidence, with the old and the new value.
How drafts follow the content language
- Drafts Ainomos builds use section headings in the content language. In English, a decision draft has Context, Options and Recommendation. A draft taken from a chat answer has Context, Question and Proposal.
- Drafts from AI apps. When an app connected through MCP, the open standard AI apps use to connect to Ainomos, proposes or revises a draft, Ainomos checks the language first. If the text is clearly in the other language, Ainomos stores nothing and asks for the text again in the content language. Short or mixed text, such as a title or a list of code, passes.
- Imported decision files. A record in the other language is not refused. The import marks it with a language warning, because a historical record stays as it was written.
- Rule messages. When a rule blocks an answer, the rules that ship with Ainomos show their title and statement in the content language. Rules your organisation wrote or edited show exactly as stored.