Skip to content
Menu

Platform

An operations layer over your entire portfolio.

Galyct MSP does not copy each client’s environment. It consolidates what needs consolidating at operator level, then lets you drill down into the client’s context when the work requires it.

Architecture

Three levels of view, from the portfolio down to a single client’s detail.

01

Portfolio

A lightweight projection of each organisation and the day’s priorities. Quick to scan, even with hundreds of clients.

02

Client 360°

A client’s posture, services, mandate, actions and governance, on a single record.

03

Client environment

The client’s in-depth business detail and its own actions, in Galyct Pro, under mandate and fully traced.

Home

My day

  • clients needing action, under watch and stable;
  • incidents and situations to handle;
  • SLAs at risk and overdue actions;
  • health of services and connectors;
  • today’s NARA briefing.
What needs my attention this morning? The operator’s home screen sorts the portfolio by real urgency: incidents, SLAs at risk, expiring mandates, silent connectors. A client that isn’t measured is never shown as stable.

Portfolio

Who needs action, and why.

Filters by criticality, service, NIS 2 obligation, owner, SLA, mandate and connector. Every status is explained and shows how fresh its measurement is. No opaque score is presented as the truth.

The portfolio reads a projection computed server-side: you only see the clients for whom you hold a mandate.

Who in my portfolio needs action? Each row states its status in plain words, its main reason and the time of its latest measurement. The status is explained; it is not reduced to a score.

Client 360°

Everything you need to know about a client, and what you are allowed to do there.

Posture by family, services operated, the mandate and its deadlines, ongoing actions, governance decisions. Access to the client’s environment takes one click, under your own account, within the scope of the mandate, and every access is logged.

Where does this client stand, and what am I allowed to do there? The record brings together posture, services, mandate and actions. To work in depth, you drill down into the client’s environment, under mandate and fully traced.

Operations

From signal to evidence, with no step lost.

Signals from your tools are normalised, deduplicated and correlated. A situation is assessed, then closed with a written decision.

  1. SignalReceived from a connected tool, normalised into a common format.
  2. SituationSignals correlated by client and by pattern, with no duplicates.
  3. DecisionAction, incident, campaign, client approval or justified closure.
  4. ActionCreated in the client’s environment, under the mandated account.
  5. EvidenceTimestamped log, with the author and reason for each decision.
Is this signal a problem, and what do we decide? Signals are normalised, deduplicated and correlated into situations. A situation is closed with a written decision: action, incident, campaign, client approval or justified closure.

Delivery

The team’s work, across all clients, without losing the context.

Board, list, workload, calendar, waiting on client and SLA. Every task keeps its client. When you are waiting on the client, the SLA clock stops, and the pause is logged.

Who does what, by when, and which deadline is at risk? Work for all clients is laid out as a board, a list or a calendar, without losing each task’s client. When you are waiting on the client, the SLA clock stops, and that is logged.

Campaigns

Same pattern, eligible clients, separate actions.

The campaign identifies eligible clients, prepares a shared fix, then opens a separate action for each client. Approval is given client by client; progress is tracked overall, evidence is kept per client.

The same problem at several clients: how do you handle it without acting blindly? The campaign prepares a shared fix, then each client approves and receives its own action, separately. Only very low-risk actions, pre-approved in the mandate, go ahead without case-by-case approval.

Incidents

The portfolio view of incidents.

Galyct MSP aggregates the phase, priority, owner, SLA and escalation of each incident. Detailed handling stays in the client’s environment: playbooks, timeline, evidence, report.

When a case is beyond your team, you request escalation to the Galyct firm, as a separate engagement.

  • phase and priority of each open incident;
  • owner and time remaining;
  • escalation requested or in progress;
  • direct link to the client’s case.

Services and SLAs

What you sold, measured.

A managed service links a commitment, a scope, controls, evidence and an SLA. Its status reads in four words: compliant, degraded, non-compliant, not measured.

Is what I sold actually being delivered? A managed service links a commitment, a scope, controls, evidence and an SLA. Its status is compliant, degraded, non-compliant or not measured, and it is reviewed monthly.

Portfolio GRC

Your clients’ compliance, at a glance.

Where each client stands on NIS 2, ISO 27001, GDPR or its own commitments, and which deadlines are approaching. The view is aggregated; the detail of controls, evidence and exemptions stays in each client’s environment. Galyct MSP does not recreate a second compliance engine.

  • portfolio compliance deadlines;
  • exemptions to renew;
  • open gaps by framework;
  • maturity assessments and their progress.

Reports

Demonstrate the work done.

Monthly reports, services and SLAs, steering committees, portfolio and campaigns. They carry your brand and the mention “Service operated with GALYCT”.

How do I demonstrate the work done? Monthly reports, SLAs, steering committees and campaigns are produced from the same data as operations: decisions, actions, evidence and progress.

NARA

An assistant that prepares and explains. You decide.

NARA analyses the portfolio, a client, an incident, a campaign, a service or your progress in the programme. It recommends, prepares, and only executes within authorised categories, after your explicit approval.

It explains before acting

The recommendation, the signals used, the clients concerned, the expected impact, the risks, the prerequisites and the approval required.

It respects isolation

Multi-client analyses rely on normalised signals, metadata and indicators. No raw data from one client is ever exposed to another.

It follows published lists

Galyct publishes and versions the list of actions that can be pre-approved and the list of actions forbidden to NARA, even after approval.

The AI provider is chosen and administered by Galyct; a partner cannot change it. The artificial intelligence engine processes data in France or the European Union.

Mandates

No access to a client without a mandate.

The mandate

  • mandatory Galyct template, optional appendices, mandatory clauses that cannot be changed;
  • start date, expiry date, revocable at any time;
  • reminders 90, 60, 30, 15, 7 and 1 day before expiry;
  • renewal only after the client’s explicit approval.

After the mandate

  • on expiry without renewal, your action rights are suspended immediately;
  • you keep read-only access to your own intervention history only;
  • a change of provider is scheduled with no overlap;
  • the client keeps the full history, without having to recreate its environment.

Mandates and transfers in detail

Client portal

Your client views, comments, approves and uploads its evidence.

In its Galyct Pro environment, your client consults its assessment, its maturity score and its history, comments, approves actions and uploads documents. It can revoke a mandate or request a transfer.

Some decisions require its approval before closure. Each approval is named, timestamped and audited: it is a formal, traceable approval, distinct from an electronic signature.

Mandatory client approvals

  • risk acceptance;
  • closure of a major incident;
  • exemption or non-compliance;
  • approval of the BCP or DRP;
  • sensitive change of scope;
  • any decision that commits the client.

Galyct sets these minimum categories; you can add more.

Team and routing

Each alert goes to the certified role that knows how to handle it.

Galyct defines the routing matrix; a critical alert can be sent to several roles. Teams, Slack and email are the normal channels.

Type of alertCertified role that receives it
Administration, connectors, exportsCertified Administrator
Posture, vulnerabilities, remediationCertified Operator
Incident, compromiseCertified Incident Operator
Compliance, risk, GDPRCertified GRC Consultant

White label

Your brand in the foreground. Galyct always visible.

Logo, colours, reports, emails, portal and domain can all be customised. Galyct remains visible everywhere, through a standard mention: “Service operated with GALYCT” or “Secured by GALYCT”. Your client always knows which platform its data relies on.

  • partner logo and colours;
  • PDF reports and emails under your brand;
  • customised portal and domain;
  • standard Galyct mention, placement set by the partner charter.

See the platform with your own roles.

The 15-day sandbox opens every role and every workflow, on an empty environment that you configure yourself.

Try 15 days in a sandbox