BEROUNOS for AI-native devices

For developers

Build the product, not the plumbing.

Write a web page, add a manifest, install it, and get a window, saved state, a background service, voice control and a place in the assistant's toolkit at once.

↗Shorter development cycles
⚙Fewer custom integrations
⬡A consistent system foundation
✦Freedom to innovate

From page to product

Four steps.

Write the page. HTML, CSS and JavaScript, with the shared platform script for the screen, the buttons and touch.

Describe it in the manifest. Name, icon, entry point, window, state, file types, place on the launcher.

Add a service if it needs a backend. When it starts, its priority, its memory budget, whether it works in sleep, whether it may take the screen.

Give Caroline tools and agents. She drives the app by voice from day one.

{ "format": 1, "id": "calendar", "name": "Calendar", "frontend": { "entry": "index.html", "window": "shared" }, "state": true, // comes back exactly where it was left "services": [{ "id": "calendard", "host": "process", "cmd": ["python3", "{app}/calendard.py", "{port}"], "start": "system", // at boot, on first open, or by hand "priority": 70, "memory_mb": 20, // stopped last, kept within budget "sleep": true // keeps working while the device sleeps }], "endpoints": [{ "path": "events", "methods": ["GET", "POST"], "service": "calendard" }], "caroline": { "description": "Calendar with events and a task list", "tools": [{ "name": "show_date", "input": {"date": "string"} }] } }

A real Beroun manifest: a page in the shared window, its state, a background service with a budget, an endpoint, and tools for Caroline.

What the platform gives an app

  • Saving and restoring state, and a clean reaction to Exit
  • Access to the memory card, sound, vibration, notifications and message boxes
  • An on-screen keyboard with layouts and voice input
  • Interface translations: the system ships in 22 languages
  • Routing of file types from the file manager
  • Manifest and state-contract checks, so every app plays by the same rules

A simulator on your own computer

  • The same manifests, shell and applications as the device
  • A virtual gamepad, touch screen, battery and memory card
  • The device's memory budget and swap, enforced on the PC
  • Several simulators side by side for multi-device scenarios
  • Development never waits for hardware

One format

There is no separate format for "system" and "third-party". Your app is described exactly like the parts of Beroun itself.

Native when you need it

Ordinary Wayland and X11 programs run under the same manifest as web apps.

The assistant is your user too

Two kinds of user, one manifest.

Every Beroun app has two users: the owner, who sees the page, and Caroline, who sees its tools and agents. Describe both in the manifest and the app works by touch, by buttons and by voice.

Tools

Small actions on the open page: show a date, open a file, play a track.

Skills

Instructions that teach Caroline how to use the app well.

Beroun

Your app. Caroline's hands.

Build once with web technologies and get an app the assistant can run.

Agents & A2ASee it on IntelliCat