Dhıya A Diwali beginning

A little light. A new beginning.

Click the ribbon or press Enter.

Happy Diwali
Design partner places are open
New beginnings, together.

Data centre operations that work as one.

  1. The power left to sell in Hall 2.
  2. The day Phase B goes live.
  3. The cooling unit drifting on row C.
  4. The one incident behind forty alarms.
  5. The GPUs running hot on rack 2B-14.
Hall 2 · 400 kW
Two open server structures in a meadow, illustrating available data centre capacity.

The system of record for the data centre.

Five systems of record

From chaos
to calm.

Five systems of record. Five versions of the floor. None of them the truth.

  • The CRM doesn't know the capacity.
  • The CMDB doesn't know the building.
  • The ticket doesn't know the rack.
  • The handover loses the data.
  • Nobody can say who changed what.
You hate · typing it twice

Re-keyed. Five times.

The same rack lives in five tools, spelled five ways. Nobody's copy is right.

You hate · the gap from alarm to invoice

Alarm. Ticket. Credit. Unlinked.

The reading, the incident and the credit sit in three systems that never met.

You hate · not knowing who changed what

Changed by someone. Sometime.

No history on the edit. Audit week means a hunt through exports and inboxes.

You hate · rip and replace

Rip it out. Start again.

Every new tool wants your old ones gone, and a year of migration before anything works.

Introducing DIL

The heart of
the data centre.

Four products come together around one shared record. From the floor to the customer, every part of your data centre stays connected.

Explore the platform

Four products. One record.

Connected at the core.

Choose a product to see how it connects to DIL and your floor.

Discover DIL →

Sell. Operate. Resolve. Compute.

Architecture

One record underneath. Four products on top. Your existing systems plugged in at the edges, not ripped out.

Four products, one record

Each product reads and writes the same objects. Nothing is copied between them.

Ayana

Accounts, contracts, metered usage, invoices and revenue.

Sell · sales, finance

Neev

Racks, power, cooling, capacity and the work on the floor.

Operate · facilities, DC ops

Vitana

Monitoring, incidents, changes and runbooks.

Resolve · NOC, IT ops

Aire

Cloud and GPU tenants: provision, meter, bill.

Compute · cloud teams, tenants

Shared by all four

What every product needs and none should own alone.

Incidents & changes

One queue. Raised from an alarm, a customer or a planned job; closed with the credit it caused.

Approvals & audit

Every approval, override and edit kept, with who and when.

Roles & access

Single sign-on, per-tenant isolation, customer views that show only their floor.

Reports & API

Dashboards, scheduled reports and a documented API over the same record.

DIL · the record

The system of record for the data centre. One ID per object, kept for life.

SiteHallRackPower pathAssetReadingAlarmCustomerContractTicketChangeCreditOne ID each
Chain of record→Reading→Alarm→Incident→Change→CreditLinked from the sensor to the bill
Multi-tenant
by design
Strongly
consistent
Every write
attributed
One object · all its linksRack 2B-14ID kept for life
HallHall 2 · Site A · row B
Power pathPDU 2B-07 → UPS B → Feeder 2
CustomerNorthwind Cloud
ContractNW-117 · 8 kW committed · metered
Open ticketINC-20417 · inlet temperature high
Last changeCHG-5531 · approved · 09:14
TenantGPU pod 4 · 12 nodes · metered
NeevAyanaVitanaAire· who writes the field

Connectors

Reads from what you already run. Each has an owner, a mapping and a mismatch report.

BuildingBMS

Cooling, environment, alarms.

PowerEPMS

Meters, breakers, UPS, gensets.

InventoryDCIM

Assets, racks, cabling.

TicketsITSM

ServiceNow, Jira and the like.

MoneyERP / finance

Invoices out, payments back.

PeopleIdentity

SSO, directories, roles.

Runs where you need it

Deployed to suit the site, not the other way round.

Your cloud or ours

Hosted by us, in your cloud account, or on the floor for air-gapped sites.

Encrypted end to end

At rest and in transit, with keys you can hold.

Yours to take

Full exports on demand. No lock-in on the record.

One record. Every workflow.

What do you use DIL for?

Capacity, power and cooling headroom in the same place the deal is written.

Today

The CRM quotes space the hall doesn’t have, or sits on kilowatts it could sell. Facilities find out at handover.

With DIL

Ayana reads live headroom from Neev: rack, power path, cooling. A quote is checked against the floor before it goes out.

“What can we sell in Hall 2 next quarter without a new feeder?”

Design partner places are open

Make contact. Map your floor. Run it as one.

Design partner places are open. Bring one hall, your BMS and your CRM, and we'll show you the chain of record on your own floor.

We reply personally. Nothing goes on a list. Privacy