The browser

The platform ships a complete browser. It is not a frame around a foreign window but a building block: you can place it next to a table, pass its content on and build it into a composite surface.

What it brings

Tabs	several pages side by side, with history per tab
Address bar	address and search in one field
Side panel	shows which connections the opened page makes in the background, and where to
Split view	results on the left, the opened page on the right — no back and forth
Profiles	own session, own sign-ins, own rules per profile
Network shares	folders on your own network in the same window
Find on page	with a hit count
Bookmarks and history	searchable, with folders

What the page does in the background

The side panel is the part that common browsers do not show: where a page connects to while you are reading it. Not as a technical log, but as a list of counterparts. If you want to block something, you block it there.

This is the browser's own firewall — it has nothing to do with the operating system's. That one is controlled by another building block, described under Computer and network (German).

Playing protected content

For video services that protect their content there is a second rendering surface. Which formats a computer can handle depends on the computer; the platform ships a check that determines it for yours instead of promising it.

Why there is no screenshot here

The browser's rendering surface is not drawn by the platform but composed by the window system. In a capture without a screen it therefore stays empty — measured with a locally loaded page: a single colour across the whole surface; with forced software drawing three, namely background and border, no text.

Every other picture on this site comes from a real build. Showing a photo with an empty middle would be misleading, and pasting a foreign page into it would be a claim. So there is a description here — until there is a real capture.

Related: Media and web · Security (German)

Technically more precise

The browser stands on the same foundation as the common browsers. Every profile gets storage of its own: own sign-ins, own cache, own permissions.

Sign-ins are deliberately kept beyond closing. That is the promise of a profile — "my account is signed in here" — and at the same time a trade-off: if you do not want it, disconnect the account or delete the credentials in the storage manager.

The side panel reads along the connections of the opened page. Blocking does not happen afterwards, but before the connection is made.

More on this: How it is built (German).