Private Beta — Early Adopter Program capabilities

2026-09. ver 0.1

INTERA is currently in Private Beta and available to selected Early Adopters.

The platform is ready for real operational use around a defined initial business problem. During the Early Adopter Program, we normally start with one focused use case, connect the required systems, build the relevant operational view, and expand from there.

INTERA is still under active development. Some interfaces and configuration workflows may change during the Private Beta.

Dashboards

INTERA provides role-based, multi-page operational dashboards.

Administrators can:

• create and edit dashboards visually;
• create multiple pages;
• assign dashboards to user roles;
• combine information from several systems;
• organise content using frames and widgets;
• control widget placement and size.

Dashboards are designed around a business role or operational responsibility, rather than around a single source system.

Widgets

INTERA includes built-in widgets for displaying:

• labels and headings;
• metrics and health indicators;
• lists and operational data;
• status information;
• actions and navigation.

The widget library is actively expanding during Private Beta.

Integrations may also provide specialised widgets for particular systems or business processes.

Integrations and DataSources

INTERA connects to external systems through its Integration framework.

Current integrations include, among others:

• generic SQL databases;
• Microsoft SQL Server;
• Oracle;
• Enigma;
• MVS.net;
• Microsoft Business Central;
• Revolut;
• Zabbix.

Additional integrations can be installed or developed separately.

Integrations expose DataSources — structured live datasets such as customers, invoices, payments, services, network information or operational records.

INTERA normally queries information from the source system rather than copying complete operational databases into INTERA.

Assets

Assets represent real business objects such as:

• customers;
• vessels;
• products;
• suppliers;
• network sites;
• accounts.

An Asset can combine information about the same real-world object from several different systems.

Asset values can be entered manually or obtained through connected integrations.

Metrics

Metrics are INTERA’s standard way of representing measurable operational information.

Examples include:

• revenue;
• account balance;
• service availability;
• utilisation;
• open issues;
• operational status;
• Asset health.

Metrics can use DataSources, calculations, conditions, other Metrics and business thresholds.

INTERA currently supports:

• synchronized Metrics;
• calculated and composite Metrics;
• Health Metrics;
• manual Metrics;
• thresholds;
• trends;
• historical values;
• data freshness and error status.

Health Metrics can combine several signals into a simple operational health indication, helping users see what requires attention first.

Reconciliations

Reconciliations compare data from two different systems and show where the records agree, differ or are missing.

They are designed for operational and financial checks such as:

• billing vs accounting;
• orders vs shipments;
• customer records across systems;
• inventory or spare-parts comparisons;
• service or usage records from different platforms.

INTERA supports field mapping, value translation and comparison rules between the two DataSources.

Instead of presenting users with a large raw mismatch list, Reconciliations calculate a reconciliation score and highlight the differences that need attention.

This makes Reconciliations suitable for repeated operational checks that would otherwise require manual spreadsheet work.

Roles and access

Users receive access through Roles.

A Role normally represents a business responsibility such as operations, finance, service assurance or management.

Different Roles can therefore see different operational views while working with the same underlying INTERA installation.

Private Beta limitations

INTERA is a working product, but the Private Beta is intentionally limited.

Early Adopter onboarding

Private Beta deployments are currently performed together with the INTERA team.

We normally begin with one clearly defined operational problem rather than attempting to model the whole company at once.

What Private Beta means

Private Beta is intended for organisations willing to apply INTERA to a real, contained operational problem, work directly with us during initial setup, and help shape the product before public launch.

If the first use case proves valuable, additional systems, Assets, Metrics, Reconciliations, Roles and operational views can then be added progressively.