AI colleagues that work inside the organization, not beside it.
A colleague is not a persona over a model. Software waits to be told what to do, every time. A colleague holds context across the systems it has been given, takes work end to end, and reports back in the language the business already uses.
Orbital is a Rhyme product. Each colleague is a distinct operating scope, shaped around a process you actually run — with its own tools, its own permissions boundary and a named person it answers to.
A colleague is defined by what it may not do before anything about what it can. Scope, permissions boundary, named counterpart, current stage — those come first, and they are the part a security reviewer reads.
That ordering is deliberate. Capability without a boundary is not something an organization can hand responsibility to, however good the output looks in a demo.
One process, defined by you. Not a general assistant pointed at the whole company and hoping for the best.
The systems it can reach and the actions it can take, granted explicitly and revocable in one place.
A person who reviews its work and owns the outcome. Accountability stays with a human being.
Where it currently sits on the responsibility ladder — read-only, drafting under review, or executing within scope.
Context that persists across systems and across colleagues, so knowledge stops living in one person's inbox.
Every action logged against a person, a scope and a stage. With no exceptions and no side channel.
Autonomy is never a switch, a pricing tier, or something granted on day one. It is earned in six observable stages, and every one of them is reversible.
You decide when a colleague advances. Orbital does not move it along the sequence, and moving it back is a single action, not a project.
Knowledge becomes accessible, expertise becomes available to everyone, and the organization gets a look at what it already knows.
We start with the business, not the technology: how the team works, which systems are used, where time is being lost, which responsibilities could be delegated.
The colleague gains access to relevant systems, documents and workflows, and builds an understanding of how the organization operates. Just like a new employee, it learns before it contributes.
It starts on practical work: preparing meetings, summarizing conversations, drafting reports and decision briefs, answering internal questions — under review.
Knowledge becomes organized, processes become shorter, repetitive work disappears. What started as support gradually becomes ownership.
It understands the business, remembers what matters, and operates across systems and teams. No longer software that people use, but infrastructure that helps the business run.
Onboarding runs six weeks and starts with a colleague that cannot change anything. Security review runs alongside it, not after it — so the clearing gate is not a surprise at the end.
Access, mapping, memory seed. Read-only throughout. The colleague learns the systems and the process before it is asked for anything.
Supervised drafts. Work goes to a named reviewer. Nothing leaves the organization or changes a system without that person.
Scoped execution, rollback rehearsed. A narrow set of actions inside the boundary — with the way back tested before it is needed.
Inside your existing commitments, not beside them. Orbital deploys within the procurement, security review and data residency arrangements you already have. There is no parallel stack to approve.
Single tenant. EU data residency. Your identity provider. Your retention policy. Every action logged against a person, a scope and a stage, and autonomy revocable in one place.
Roles are yours to define. The five below are worked examples — the ones we have built often enough to describe — not a fixed roster. Most organizations end up with at least one colleague shaped around a process only they run.
One colleague is a tool. Several colleagues sharing one memory, one permissions model and one audit trail is infrastructure — and that is the part worth buying.
Orbital is built by Rhyme, in Stockholm. We are a development-first consultancy that has shipped production software for companies like PostNord, ATG, Zound Industries and Fujifilm, and we run our own products in production — Orbital alongside Meld, our subscription and membership platform.
That matters here more than it usually does. Deploying colleagues inside an organization is an integration problem, an identity problem and an operations problem before it is a model problem. It is the work we already do.
Working out which responsibilities could be handed off?
That is the conversation to start with — not a demo. Tell us the process you have in mind and we will walk through what a colleague would be allowed to do in the first six weeks, and what it would not.
hello@rhymesthlm.se
+46 73 525 81 05
Working out which responsibilities could be handed off?
That is the conversation to start with — not a demo. Tell us the process you have in mind and we will walk through what a colleague would be allowed to do in the first six weeks, and what it would not.
hello@rhymesthlm.se
+46 73 525 81 05