Introducing Orbyna: A Connected Operating System for the Entire Organisation

Modern businesses have no shortage of software. Project teams have one platform, sales has another, HR has its own system, documents are stored somewhere else, conversations happen across multiple channels, and leadership often relies on dashboards and reports assembled from all of them. Individually, these tools may work well. The problem begins when the organisation itself has to operate across the gaps between them.

That fragmentation creates a hidden layer of work. Teams copy information from one system to another, access has to be configured repeatedly, decisions lose their original context, reports are reconstructed from several data sources, and something as simple as understanding the current state of a project can require multiple applications and several conversations.

At Metaveo, we saw an opportunity to rethink that model rather than add another application to the stack. The result is Orbyna, a connected operating system designed to bring the different functions of an organisation into a shared operational environment. Instead of treating project delivery, customers, people, communication, knowledge and governance as unrelated categories of software, Orbyna connects them through one identity model, one operating record and one administration layer.

One operation, nine connected systems

Orbyna is being built around nine connected systems: Project Management, CRM, Organisation, HRMS, Productivity, Documents, Communication, Learning and Administration. Each system is designed to provide the depth required by the teams using it, while sharing context with the wider organisation. Projects, Productivity and Administration are currently live, Organisation is in beta, while CRM, HRMS, Documents, Communication and Learning are being introduced as the product universe expands.

That distinction is important. Orbyna is not intended to be a collection of simplified mini-apps bundled under one interface. The platform is designed around what Orbyna calls a shared operating memory: identity, workflows, linked context and operational evidence persist across its systems. Members, roles, permissions, approvals, automation, relationships, activity histories, versions and audit trails can therefore remain connected instead of being recreated every time work crosses from one department to another.

The result is a different way of thinking about business software. A customer can remain connected to the deal that brought them in, the project created to deliver what was promised, the people responsible for that work, the conversations and documents surrounding it, and eventually the evidence showing how that work was completed. The context survives the handoff.

Project management built beyond boards and tasks

Orbyna's Project Management System is one of the platform's live systems and provides a good example of the depth behind the wider product vision. It is designed to manage the complete journey from strategic direction to delivery evidence rather than stopping at task management. Portfolios, programmes, projects, roadmaps, goals, milestones, budgets and project health can sit above the day-to-day execution layer, giving leadership a way to understand both direction and delivery from the same project record.

At execution level, teams can work with backlogs, Kanban boards, sprints, sprint goals, capacity planning, dependencies, milestones, releases and custom workflows. Timeline and Gantt views provide scheduling and critical-path visibility, while sprint velocity, burndown, cycle time, workload and other operational signals help teams understand how work is actually moving. Custom statuses, transitions, conditions, approvals, notifications and trigger-based actions allow workflows to reflect the way an organisation operates rather than forcing every team into the same process.

Quality is also treated as part of delivery rather than a disconnected phase. Requirements, test cases, test suites, execution runs, defects, regression scope, approvals and release readiness can remain linked to the project they belong to. Teams can maintain requirements traceability, meeting notes, project discussions, whiteboards, decisions and versioned project knowledge alongside the work itself. Time tracking, timesheets, estimates, billable hours, project budgets, rates and project-level invoicing extend that same record into the commercial side of delivery.

Orbyna also introduces AI-assisted operational intelligence into this layer. Rather than using AI as a separate chatbot sitting beside the product, the intention is to use it against operational context to identify delivery risk, explain changing conditions, surface priorities and guide attention toward issues that may require action. The wider platform describes this as early-warning capability around dependencies and critical paths, allowing potential slippage to become visible before it eventually appears in a conventional status report.

Connecting revenue to what happens after the sale

The upcoming Orbyna CRM extends that same operating model into the customer lifecycle. It is designed to cover companies, contacts, leads, qualification, deals, pipelines, products, quotes, campaigns, forms, activities, conversations, contracts and renewals rather than functioning as an isolated sales database.

Leads can originate from forms, campaigns, imports, conversations or manual entry, retain their source and ownership, move through qualification and eventually become opportunities inside configurable pipelines. Deals can carry value, probability, stages, forecasts, expected close dates and audit history. Product catalogues, line items, discounts, tax and deal-linked quotations add commercial context, while campaign attribution and embedded forms connect demand generation to the records that result from it.

Customer communication is designed to remain part of that history as well. Email, SMS, calls, WhatsApp, meetings, activities, contracts, renewal dates and expiry alerts can sit within the same customer timeline. More importantly, when a sale turns into delivery, the promises and context created during the sales process can move into connected project work rather than disappearing during the handover between sales and operations.

Making organisational structure part of the system

Most software knows who a user is, but far less of it understands where that person sits within an organisation. Orbyna's Organisation system, currently in beta, is designed to model that structure directly. Legal entities, business units, locations, teams, designations, reporting relationships, services and staff profiles can form a living organisation graph that other Orbyna systems can reference.

This makes organisational structure more than a directory. Roles can be defined around actual operational responsibilities, while permissions can be controlled at module and action level for viewing, creating, editing, deleting and administration. The same staff profile can then connect to project ownership, tasks, CRM records, HR information and conversations. When responsibilities or structures change, the organisation model can evolve without requiring separate identity systems to be reconstructed across multiple applications.

Orbyna also supports founders operating more than one business. A single founder account can manage multiple organisations, while each business retains its own separate Orbyna instance, people, work, data, settings and permissions. This provides a common point of access without collapsing the boundaries between separate companies.

HR that connects people operations to actual work

The planned HRMS takes the employee lifecycle from recruitment through separation and connects it to the wider organisational record. Its scope covers employee records, recruitment, onboarding, attendance, leave, shifts, rosters, payroll, benefits, performance, assets, expenses, travel, policies, compliance and employee service.

Recruitment workflows can manage jobs, candidate pipelines, interviews, offers and onboarding milestones. Once someone joins, their employee history, documents, confirmation, promotion, transfers and assets can remain part of the same record. Attendance and workforce management extend into shifts, rosters, punches, regularisation, overtime, work-from-home policies, comp-off and holidays, while payroll covers salary structures, earnings, deductions, payslips, tax declarations, loans, claims and benefits.

Performance and development are designed to connect back into the employee's wider context. OKRs, appraisal cycles, self-assessment, manager reviews, ratings, check-ins and supporting evidence can sit alongside learning and career development. Employees also receive a self-service environment for requests, attendance, payslips, learning, documents, travel, expenses and company assets.

Productivity without creating another disconnected task list

Not every piece of work belongs inside a formal project. Orbyna's live Productivity system is intended for the smaller commitments, reminders and focus activities that make up a working day. Personal to-dos, tags, Pomodoro-style focus sessions, a unified calendar and persistent sticky notes provide a lightweight personal layer without forcing every thought or task into a project-management workflow.

The difference is that these tools still sit inside the wider operating environment. The calendar can combine meetings, project deadlines, leave and custom events, with direct links back to their source records. A personal item can remain lightweight or be promoted into shared work when it becomes important enough to require collaboration. The personal command view then brings priorities, schedule, focus state and unread signals into a single place for the individual user.

Documents that retain their business context

The upcoming Documents and Content system extends Orbyna into file storage, collaborative writing, spreadsheets, forms and visual collaboration. The purpose is not simply to recreate familiar office applications inside another interface, but to stop knowledge from becoming detached from the work that produced it.

Orbyna Drive is designed around team file storage with folders, previews, versions, sharing permissions, public links and usage tracking. Writer provides collaborative, block-based documents for material such as proposals, SOPs, requirements, reports and internal knowledge. Sheets supports formulas, formatting and import/export workflows, while Forms introduces conditional logic, file collection, response analytics, links and embeds. A collaborative whiteboard provides an infinite canvas for planning, diagrams, maps, retrospectives, wireframes and other forms of visual thinking.

What ties these tools back to Orbyna's broader philosophy is contextual knowledge. A document does not have to live as an isolated file whose meaning depends on its folder name. Content can be attached directly to projects, requirements, customers, employees, training and other operational records, preserving why it exists and what it supports.

Communication that remains attached to action

Business conversations contain decisions, approvals, context and commitments, but much of that information is lost inside disconnected messaging tools. Orbyna's upcoming Communication system is designed around keeping conversation attached to the work it affects.

Team messaging includes channels, direct messages, threads, mentions, reactions, file sharing, code snippets, presence and search. A unified inbox brings assignments, approvals, mentions and alerts from Orbyna's different systems into one chronological action centre. Notification controls allow users to filter, snooze, archive and tune signals by module or event type rather than treating every notification as equally important.

WhatsApp Business communication is also planned as part of this layer, including media, templates, delivery states and automatic links to CRM contacts. Contextual threads can remain attached to projects, issues and customer records, while searchable conversation history preserves participants, files, decisions and follow-up actions. In practice, a conversation about a project can remain a part of that project's history instead of becoming something the organisation has to reconstruct later.

Turning learning into visible organisational capability

Orbyna's Learning system is being designed to connect training with employees, roles, compliance and development rather than treating learning as a separate portal. Courses can include categories, materials, prerequisites, trainers, locations, sessions and assessments, while learners can browse available programmes, enrol, attend, complete assessments and monitor their progress.

Certificates can be generated and retained against employee learning records, while compliance programmes track required training, completion, expiration, renewals and gaps across the organisation. Induction programmes can combine policies, videos, quizzes, meetings and tasks into structured journeys for new employees. Learning can also be connected to roles, skills, personal goals, appraisal evidence and career development, allowing training activity to contribute to a broader picture of organisational capability.

One administration and governance layer underneath everything

For a connected platform to reduce software complexity, administration has to be connected too. Orbyna's live Administration system provides the control layer for workspace configuration, members, roles, integrations, security, billing and governance.

Organisations can configure branding, language, timezone, defaults, project templates, CRM pipelines and other operating conventions from the workspace. Member administration covers invitations, status, roles, activity, deactivation and ownership transfer, while security controls include password policies, two-factor authentication, active sessions, session termination and configurable timeouts. Audit and master-data capabilities cover terminology, custom fields, reference data, execution logs, permissions and traceable change history.

Orbyna is also designed to coexist with systems an organisation chooses to retain. Its integration layer includes guided connections for platforms such as Jira, Monday.com, GitHub, GitLab, Bitbucket, SendGrid and Twilio, with the broader product vision focused on connecting projects, developer workflows, communication and customer systems without removing their original context.

The larger idea behind Orbyna

The value of Orbyna is not simply that nine categories of software can eventually exist under one subscription. Consolidation alone would solve only part of the problem. What matters more is what becomes possible when those systems understand the same organisation.

A member does not need to become a different user in every application. A customer does not need to lose context when sales hands work to delivery. A project does not have to separate its tasks from its requirements, testing, conversations, time and commercial information. A leadership report does not have to begin as an exercise in collecting and reconciling information from several different systems.

Orbyna is designed so that identity, workflow, context and evidence travel with the work. Leadership can move from a portfolio-level signal to the project, record, person, decision or control behind it. Teams can retain the depth they require without creating an entirely separate operational universe for every department.

There is also a commercial consequence to that model. Instead of maintaining numerous accounts, permission models, invoices, contracts, integrations, access reviews and renewals, Orbyna is structured around one subscription and one administration surface. Its current private-preview plans are based on active staff rather than charging separately for each module, with Complete and Enterprise intended to receive additional Orbyna systems as they are released.

Built by Metaveo

Orbyna represents a significant step in Metaveo's evolution from building digital experiences and software solutions to creating a product designed around a much larger operational problem. It brings together product strategy, UX, software engineering, automation, data, AI and business-process thinking in a platform whose ambition is not to improve one department in isolation, but to make the organisation itself easier to understand and operate.

The product is already taking shape through its live Projects, Productivity and Administration systems, with Organisation in beta and CRM, HRMS, Documents, Communication and Learning forming the next stages of the platform. Orbyna is currently available through private preview as that product universe continues to grow.

For organisations that have outgrown fragmented tools, duplicated administration and disconnected operational data, the proposition is straightforward: fewer systems to piece together, more context that survives from one part of the business to another, and a clearer view of what is actually happening across the organisation.

See everything. Steer anything.

Explore Orbyna at orbyna.ai.