Tessera

Know what you run. Control what changes. Fix what breaks.

Tessera is service management built on a CMDB you define, with change management and ticketing for broadcast, media and IT teams.

Book a demo
Tessera asset list: the records in a CMDB, with status, criticality, lifecycle, rack and model. Demo data from a fictional broadcast and teleport operation.

Know what you have. Plan what changes.

A connected operational record for the people responsible for your infrastructure.

Model your real world

Build around your own asset classes and dependencies, then evolve the model as your infrastructure changes.

Change with confidence

Move from draft to coordinated change set to scheduled application, with revalidation and a history you can inspect afterward.

Answer the operational question

Turn connected records into saved queries, role-specific dashboards and scheduled reports for engineering and operations.

One platform, three jobs

Know what you run

A CMDB that fits your operation, with your own classes, attributes and relationships.

  • Record and relationship history, with undo
  • Stage edits as drafts and apply them on a schedule
  • Dashboards, reports and calendars
  • CSV import and a documented REST API

Control what changes

See what a change touches before you approve it.

  • Normal, standard and emergency change models
  • Impact analysis across CMDB relationships
  • Approvals, risk scoring and CAB meetings
  • Blackout and maintenance window conflict checks
  • Detection of edits with no approved change behind them

Fix what breaks

A service desk that already knows what each ticket affects.

  • Incidents, requests, problems and major incidents
  • SLAs on your own working calendars
  • E-mail intake and rule-based routing
  • A requester portal and service catalog, with no licensed seat for requesters
  • One incident from repeated monitoring alerts

Every asset, with its context.

Each asset is a record in a CMDB you shape yourself. Open one to see its details, relationships, history, tickets and changes in one place.

One asset.A power amplifier, with tabs for relationships, history, tickets and changes. The blackout and maintenance windows that apply to it are listed on the right.
See 7 more screensRelationships, History, Tickets, Changes, Your own data model, Add an attribute, Add an asset type
Relationships.What it is mounted in, what powers it, what it supports and what it feeds.
History.Every update, with who made it and the values before and after.
Tickets.The open incident and the problem raised against this asset.
Changes.Changes planned against it. One is flagged with a conflict, because it falls outside the maintenance window.
Your own data model.In the administration interface, each class has typed attributes, with columns for what shows in the grid and detail card, what is unique or mandatory, and what is editable.
Add an attribute.A decimal frequency in MHz: its type, precision and unit of measure are set here.
Add an asset type.A new class that inherits from Equipment, so it starts with the attributes Equipment already has.

Model what you actually run.

Define classes, attributes and relationships in the administration interface, with inheritance and typed attributes such as IP addresses, lookups and references.

  • Sites
  • Racks
  • Devices
  • Circuits
  • Services
  • Multicast addresses

From draft to done.

  1. Draft

    Begin with the affected entries and stage your edits as drafts.

  2. Draft set

    Combine related drafts when a change touches several records.

  3. Schedule

    Schedule application for the agreed window.

  4. Revalidate

    Tessera revalidates the scheduled changes before applying them.

  5. Apply

    The validated changes apply in the agreed window.

  6. Review

    Inspect entry history and the separate relationship history.

See what a change touches before you approve it.

A change request reads the same records and relationships. It shows what is affected, which services depend on it, and whether it clashes with a blackout or a maintenance window.

Impact graph.The records the change touches on the left, and what depends on them to the right, down to the services.
See 7 more screensBlackout conflicts, The change record, Approval, Affected records, Impacted services, Change calendar, The clash, by the hour
Blackout conflicts.Eleven conflicts block this change. Each names a record inside a blackout window, or whose parent is, with an override on each.
The change record.A normal change to replace a module in a power amplifier. The record shows its risk rating, what must be resolved before it can be scheduled, and the planned window.
Approval.A change advisory board approver has approved, with a comment.
Affected records.The records this change works on.
Impacted services.Found by following relationships, with how many steps away each one is.
Change calendar.Changes and maintenance windows for the month. The change in the hatched blackout is the one with conflicts.
The clash, by the hour.The same change in the week view, overlapping the blackout window.

Tickets that know what they affect.

Incidents, problems and requests share one service desk, each tied to the records it affects. People who report issues and ask for services use a portal and a catalog, with no licensed seat.

The service desk.All open tickets in one queue: incidents, problems and requests, with priority, assignment group and time to breach.
See 4 more screensThe requester portal, The catalog, A request form, My requests
The requester portal.Report an issue, request something, follow your requests and read service announcements.
The catalog.Services grouped by what people ask for: broadcast services, hardware, software, access and facilities.
A request form.Booking satellite capacity: pick the beam and bandwidth, then the dates.
My requests.Everything a requester has asked for, with its latest status.

From a Mosaic alarm to an incident.

Tessera has an alert API with a ready-made Mosaic source. An alarm can open an incident tied to the affected device, and repeats add to the same incident.

The incident.A critical incident for a power amplifier output fault. Its requester is the Mosaic alarm integration, and its priority and SLA follow from the impact and urgency.
See 3 more screensWhat it affects, What changed nearby, Impact on a graph
What it affects.Three records impacted, reaching three business services.
What changed nearby.Open tickets on the same records, and recent changes to them.
Impact on a graph.The failed amplifier and its antenna on the left, and the business services they reach on the right.

Know what is in every rack, and what depends on it.

Sites, racks, devices, circuits, services and multicast addresses, modeled the way you run them, with the history of every change.

Common questions

Is Tessera a CMDB or a service management tool?

Both. The CMDB is the base. Change management and ticketing are modules that work directly with its records and relationships, so you can start with what you need.

Does it cover everything a large ITSM suite does?

It covers the core: CMDB, change, incidents, problems, requests, a catalog, a portal and SLAs. It does not include a knowledge base, automated discovery, a visual workflow designer, on-call or AI features.

Does it work with Mosaic?

Tessera has an alert API with a ready-made Mosaic source, so Mosaic alarms can open an incident tied to the affected device, and repeats add to the same incident. Other monitoring tools can use the same API.

Can we host it ourselves?

Yes. Tessera runs on your own servers or in Docker, on Windows or Linux, with a PostgreSQL database.

How do users sign in?

With Tessera accounts or your LDAP directory. API clients use OAuth2 tokens.

Go deeper

Model your infrastructure

A model that fits your infrastructure

Define classes, attributes and relationships in the administration interface. Model sites, racks, devices, circuits, services and multicast addresses, with inheritance and typed attributes, including IP addresses, passwords, lookups and references.

Relationships with real context

Store information on the relationship itself, such as a device’s rack position. Combine controlled lookups, derived display attributes, custom entry layouts and unique constraints to keep your model consistent.

Build a useful infrastructure model

Start with one representative site and a few classes such as racks, devices, circuits and services, use inheritance for the fields they share, and store link details, such as rack position, on the relationship itself.

Find and bring in records

Find answers across your estate

Search globally, traverse relationships and build reusable filters with CQL. Advanced SQL and JavaScript filtering helps specialists ask deeper questions of connected operational data.

Move from existing records to maintained data

Import entries and relationships from CSV, check them with saved filters and built-in validation, and agree naming, ownership and unique fields before you import the rest of the estate.

Plan and track change

Plan changes before they go live

Stage edits in drafts, coordinate multiple records in a draft set and schedule application. Tessera revalidates scheduled changes before applying them, helping teams prepare work ahead of a maintenance window.

Keep the operational calendar connected

Bring draft changes, reports, flows, email jobs and attribute-based markers into day, week and month views. Schedule recurring work and notify watchers when plans change.

History and access

Know what changed and who changed it

Inspect timestamped entry history with highlighted attribute differences, revert changes and recover deleted entries. Relationship history provides a separate record and undo path for relationship changes.

Access control at the data level

Configure permissions for classes, attributes, relationships, rows, reports and menus. Use internal accounts or LDAP / Active Directory authentication, with roles managed inside Tessera.

Work as a team

A shared workspace for your team

Use configurable grids, saved filters and record locking to coordinate daily work. Bulk-edit common, non-unique attributes, preview attachments and view live HLS video or refreshing device thumbnails within an entry.

Give each team the right working view

Agree the records and actions each role needs, set permissions, menus and dashboard defaults to match, and sign users in with LDAP or Active Directory while their roles stay in Tessera.

Reports and dashboards

Reports that reach the right people

Build parameterized JasperReports, control access by role and schedule delivery. Export reports as PDF, XLSX, CSV, DOCX, RTF or HTML, and export filtered grid views to PDF or CSV.

Dashboards shaped around each role

Arrange grids, schedules, reports, activity and links with drag-and-drop widgets. Set system and role defaults while letting users personalize their workspace.

Plan reporting and operational handovers

Turn the questions each team asks every week into saved queries or scheduled JasperReports, with report permissions by role, and keep record history and attachments for handovers between teams.

Connect other systems

Connect to your wider ecosystem

Connect through a documented REST API with OAuth 2.0 and dedicated machine users, signed webhooks and CSV import of entries and relationships, and send templated e-mail. MNC can also build plugins for external services.

Choose how to deploy

Operate on your terms

Deploy on Windows, Linux or Docker. Combine configurable built-in validation, scheduled backups, selective restore and audit records with localized data labels and branding. Feature availability depends on your license.

Choose the deployment scope

Install on Windows or Linux, or with Docker, on PostgreSQL, and tell us your record and user counts, integrations, backup approach and the modules you need, so the license matches.