Skip to main content
GiniLytics IT Solutions logo—Matrix

From GiniLytics IT Solutions

Delivery, people and pipeline in one workspace

Matrix is the work platform for IT services and software delivery companies. Run projects on a board, log the hours against the issue they belong to, and keep attendance, leave, hiring, CRM and hardware in the same tenant — so the report on what a project cost reads the same records your team works in every day.

Create your workspaceSee what it does

Free, Pro and Enterprise plans. How pricing works · Log in

Illustration of the Matrix board: the product's default To Do / In Progress / QA / Done columns, which each project can replace with its own stages. Placeholder issues, not customer data.

Why one workspace

The expensive part is the gap between your tools

Delivery in one system, timesheets in another, HR in a third, CRM in a fourth. Each one is fine. The cost is the reconciliation between them — and it lands at month end, every month.

One record, not four

The issue on the board, the hours on the daily report, the approved leave and the person’s reporting line are rows in one database, behind one company boundary. Reports cross those areas because there is no boundary to cross.

Hours attached to real work

Time is logged against a project and a specific issue. That is what turns a timesheet into something you can learn from: estimate against actual, rework against new work, sprint against reality.

One access model

A named permission per screen and per report, one catalogue, custom roles, and per-project access on top. One place to grant it, one place to review it, one place to remove it.

What is in it

Nine areas, one product

These are the product’s own modules, not a marketing taxonomy. Each links to a page describing exactly what it does — see all features.

Project management

Boards with configurable stages, a planned backlog, epics, sprints and issues with their own keys and history.

Learn more

Daily Status Reports

Each day's work logged against a project and a specific issue, with hours, status and a description.

Learn more

Attendance & leave

Attendance imported from your device's own export, plus leave types, holidays, approvals and balances.

Learn more

Reports & analytics

Hours per project, effort allocation, sprint analytics and attendance reporting — no export step.

Learn more

CRM & pipeline

Organisations, contacts, leads and deals, with documents, product demos and team resumes attached.

Learn more

Hiring & talent

Applicants with CVs, the employee directory, documents, notes and a reporting hierarchy the product uses.

Learn more

Asset management

A hardware register with available, allocated and in-repair counts, allocated to employees as packages.

Learn more

Portfolio & enterprise

Backlogs and boards above a single project, for teams running several engagements at once.

Learn more

Roles & permissions

One named permission catalogue driving the sidebar, the routes and the API — with custom roles.

Learn more

The habit that makes the reports true

Two minutes a day, and month end stops being an event

A Daily Status Report names the project, the issue, the hours, the status and what actually happened. It takes recognition rather than recall — the issue is in a picker, because it is the issue they were working on.
  • Several entries a day, totalled automatically
  • Preview before it is emailed, with extra recipients per submission
  • Missing DSRs is a report, so chasing is a five-second check
  • An optional enforcement lock, switched on per company
  • Every user can switch the emails off for themselves
How Daily Status Reports workTracking billable hours per project
Illustration of the Add DSR screen: hours are logged against a project and a specific issue, and the day's total is what the summary email reports. Placeholder entries.

Use cases

What teams actually open it for

Six things that are hard when your systems disagree, and ordinary when they do not.

Close the month without a spreadsheet

Hours Per Project and Effort Allocation read the Daily Status Reports the team already filed. The number you report is the number in the system.

See the reports

Know what a client engagement cost

A project carries its client hours, internal hours and monthly estimate. The hours logged against its issues are compared to them, not to a memory.

For IT services companies

Plan a sprint knowing who is away

Upcoming leave, company holidays and the team calendar are in the same product as the backlog you are planning from.

For delivery managers

Stop reconciling attendance by hand

Upload the attendance machine's own export — .xls or .xlsx — correct the exceptions, and report on the result.

Attendance and leave

Hand over a won deal without losing the detail

The deal, its documents and the demos you gave are in the same workspace as the project team who will deliver it.

CRM and pipeline

Offboard someone in one place

Their access, their projects, their leave record and the equipment allocated to them are all on the same employee record.

Asset management

Who it is for

One workspace, several jobs

Everyone gets their own dashboard and their own work. What else they see is a role built from the permission catalogue.

IT services companies

Client hours, delivery, HR and pipeline in one tenant, with the month-end reports reading the same records.

Read the solution

Delivery and engineering managers

Sprint progress, cross-project workload and where the hours actually went — without a spreadsheet in the middle.

Read the solution

HR and people operations

Attendance imported rather than transcribed, leave with a trail, documents on the person, and an org chart the product uses.

Read the solution

Integrations

Connects to the infrastructure you already run

Your mail server, your object storage, your attendance devices and your document library — Matrix fits into your estate rather than asking you to move to someone else's.

  • Your SMTP server

    Every email Matrix sends goes through an SMTP server you configure, with templates you can edit and a log of every attempt.

  • S3-compatible object storage

    Uploaded files are stored in AWS S3 or any S3-compatible endpoint you run yourself, as tenant-owned objects.

  • Attendance machine exports

    Upload the spreadsheet your attendance device produces and Matrix reads it — no template to fill in, no retyping.

  • SharePoint document links

    A project can carry its SharePoint URL, so the team gets to the document library from the project record.

  • Anthropic Claude

    Powers the open-ended answers in Gini Assistant, so your team can ask questions in their own words.

  • REST API with OpenAPI documentation

    The product's own HTTP API, documented with Swagger, behind the same authentication and permission checks as the interface.

What each integration does

Security

Your workspace, and only yours

Every record belongs to exactly one company, and that boundary is enforced in the data layer itself. Here is what that means in practice.
Read the security page

Company scoping on every query

Each request carries the company it belongs to, and the data layer requires it before a query runs — so your workspace returns your workspace's records.

Sessions you cannot read from a page

Tokens are delivered as cookies with separate idle and absolute timeouts, and a refresh token is checked against the device it was issued to.

Files belong to your company

Every upload is a record with an owner, and both download and delete confirm the requester belongs to the company that owns it.

Role-based access throughout

One named permission per screen and per report drives the navigation, the route and the API — with custom roles and per-project access on top.

Optional

Gini Assistant: ask, inside your own permissions

Some questions are faster asked than navigated to. The assistant answers them in the session you are already in — and most of them never reach a model at all, because a count is something a database computes exactly.
  • No second login: it runs behind your existing session
  • Permissions checked before any work, and again in the service underneath
  • A fixed set of tools registered at startup — no generated SQL
  • Destructive actions come back as a signed confirmation, not an outcome
  • Every write audited, including failures; no question text in logs or metrics
How the assistant works

What people ask it

  • “What is assigned to me this sprint?”
  • “Which tasks are overdue on the client portal project?”
  • “How many open bugs do we have, by project?”
  • “What percentage of this sprint is done?”
  • “Summarise where the migration project stands.”

The direct ones are answered straight from your own data in a single query. Everything it does stays inside the asker’s permissions.

From the team

Writing about the problems the product exists for

Practical pieces on time reporting, attendance, access control and evaluating AI assistants — written by the people who built these parts of Matrix.

Daily status reports people actually submit

A DSR habit dies for predictable reasons. Here is what to ask for, who should read it, and when enforcement is justified.

6 min read

Designing a role and permission model that survives contact with your team

Before you tick a single box: how to decide what your roles are, and why the menu is the least important layer.

8 min read

Getting attendance data off spreadsheets

The device already has the data. The expensive part is everything that happens to it afterwards.

6 min read

All articles

Questions

Straight answers

The questions teams ask us most often when they are working out whether Matrix fits.
What exactly is Matrix?
A multi-tenant web workspace for companies that deliver client work. It covers project delivery (boards, backlogs, epics, sprints, issues), Daily Status Reports with hours, attendance and leave, an employee directory and reporting hierarchy, CRM, hiring, hardware asset allocation, and reporting across all of it.
Who is it built for?
IT services and software delivery companies. The product models client names, client hours, internal hours and monthly estimates on projects, and reports on hours per project and effort allocation — which is the way a services business keeps score.
Do we have to use all of it?
No. Access is granted through roles built from a named permission catalogue, and plans control which modules are available. A company can use the delivery side and leave the CRM unused, or the reverse.
Is there a free plan?
Yes. Matrix has Free, Pro and Enterprise plans. Free and Pro are self-serve, and Enterprise is arranged with the team so the limits and modules are shaped around your organisation.
What does Matrix integrate with?
Matrix connects to the infrastructure you already run: your own SMTP server for product email, S3-compatible object storage for files, attendance-device spreadsheet exports, SharePoint document links on a project, an AI provider for the assistant, and a documented REST API your team can build on.
Can we control who sees what?
Yes. Every screen and report has its own named permission, roles are built from that catalogue, and project access is granted per project on top. The same permission guards the menu, the route and the API independently.

Put the whole month in one place

Create a workspace, invite your team, and run one project through it. The reports will tell you within a month whether it matches what you believed was happening.

Create your workspaceTalk to us first

Already using Matrix? Log in, or compare the plans.