I'm new here
Meet Ronja in a conversation, learn your way around, and get your first data flowing.
Everything in Ronja starts with a conversation. You ask a question in plain language, and Ronja — the agent — finds the data, does the work, and shows you the answer with the numbers to back it up. When an answer is worth keeping, Ronja builds it into something permanent: a table that stays fresh, a workflow that re-runs on its own, an app your whole team opens.
But a conversation is only half of it. Ronja also works when nobody’s asking: automations wake the agent when something happens — a schedule fires, an email lands in a connected mailbox, a table refreshes — and hand it the context to act. That’s how a case gets triaged before anyone has read it, or a data mismatch pings its owner the day it happens instead of at month-end.
Underneath sits a governed foundation: connections that sync your sources on a schedule, features that bundle related work, access groups that decide who sees what, and approvals that keep a human in control of anything important. Everything you and Ronja build — tables, workflows, apps, automations, knowledge — stays in the platform and keeps working.
Pick the path that matches where you are today.
I'm new here
Meet Ronja in a conversation, learn your way around, and get your first data flowing.
I want to build
Turn one good answer into assets your team reuses every day — and automations that run without you.
I run the organization
Bring your team in, assign roles, share the right data with the right people, and govern AI spend.
For the tech team
How Ronja replaces the traditional stack, and how it stays accurate.
Looking for a definition? Try the glossary. Mixing up two similar concepts? What’s the difference? untangles the usual pairs.