About MetaSym

Software should follow the operating model.

Too often, organisations must fragment their work across spreadsheets, forms and systems designed around someone else's assumptions. MetaSym is being built from a different starting point: understand the domain, model it clearly, then shape the experience around it.

Our premise
Operational software becomes more useful when data, interface, action and access share the same underlying definition.

Why MetaSym exists

Real operations rarely fit a fixed software category. The same organisation may need to manage equipment, coordinate other organisations, collect evidence, guide people through work and control access to sensitive actions.

Building a separate application for each process creates duplicated models and disconnected histories. Forcing every process into one fixed product creates compromises elsewhere. MetaSym explores the space between those extremes: a consistent platform that can express distinct operational Experiences.

Design principles

What guides the platform.

Start with the domain

Understand the things, events, decisions and relationships before deciding what the screen should look like.

Keep the model connected

Data definitions, interfaces, actions and permissions should reinforce one another rather than drift into separate systems.

Make governance explicit

Who can see and act is part of the experience definition, not an afterthought applied only in the interface.

Let experiences evolve

Operational processes change. Configuration should support refinement while preserving validation, history and human review.

How it takes shape

One platform.
Many purposeful experiences.

MetaSym combines five building blocks inside an organisation context: Assets, Events, Actions, Views and Permissions.

Those blocks support experiences for different domains while preserving a consistent way to define information, interaction and control.

Explore the platform

Built openly and deliberately

MetaSym is an actively developed platform. Core model-driven capabilities are implemented, while domain Experiences continue to be designed, tested and refined.

This website intentionally distinguishes platform capability from domain maturity. It does not present development Experiences as finished customer case studies or promise complete coverage where work remains underway.

A useful starting point

Bring the operational problem.

The best conversation starts with what your organisation manages, records, decides and needs to control.

Discuss your workflow