Start a Free 30-Day Sensaka Pilot
In four weeks, Sensaka DCOS monitors up to 200 of your servers through their BMCs, inside your network, against success criteria you set before we start. The pilot is free.
This is not a hosted demo. It runs on one VM you provide, reads your real hardware, and ends with a written report and a decision meeting. Technical support throughout the four weeks comes from Sensaka engineering. If the numbers do not hold up, you have lost four weeks and nothing else.
What the Pilot Covers
The pilot is deliberately narrow. It proves the layer most monitoring stacks cannot see: the physical server below the operating system. Everything else in the platform can be shown later, once the hardware signal is trusted.
Out-of-band hardware monitoring (DCOS)
Agentless monitoring of up to about 200 physical nodes through their BMCs: Dell iDRAC, HPE iLO, Lenovo XClarity, Huawei iBMC, Supermicro and Cisco, over IPMI, Redfish or SNMP. No software on the host OS.
Discovery and inventory
DCOS reads model, serial number, firmware and component health directly from the management controllers. You get an inventory you did not have to type.
Optional: iDCOS CMDB
If you want to see the IT operations layer, the discovered inventory can be loaded into the iDCOS CMDB through Sensaka Sync and compared with your existing asset records.
What You Provide
Three things, all of which your team controls. Nothing is exposed to the internet and no agent is installed on a production host.
BMC network access
Routed access from the pilot VM to the BMC management network (IPMI/Redfish ports). A separate VLAN is fine; most pilots run inside it.
Read-only credentials
One monitoring account per BMC vendor with read-only rights. No root or administrator credentials are needed for the monitoring pilot.
One virtual machine
One Linux VM on your own hypervisor. Sizing for your node count is confirmed in the scoping call before week one.
Week by Week
- Week 1
Install and discovery
DCOS is installed on your VM. We connect the first BMCs together, then let discovery run across the agreed node range. End of week: a verified inventory and a list of hosts that did not respond, with the reason.
- Week 2
Baselines and alerting
Power, temperature and component health baselines are collected. Alert thresholds are set with your team, and alerts are routed where you already work: PagerDuty, OpsGenie, Slack, Jira or a webhook.
- Week 3
One real incident or a fire drill
Either a real hardware event occurs or we stage one: pull a redundant PSU, fail a fan, or disconnect a disk on a test host. We time how fast the signal reaches your on-call channel and how clear it is.
- Week 4
Review and report
A written report against the success criteria agreed in week zero: coverage, time to detect, false positives, open gaps. One review meeting with the people who will decide.
Success Criteria Agreed Up Front
Before anything is installed, we write down with you what a pass looks like. The week-four report is measured against that page and nothing else. Typical criteria:
After the Pilot
You keep the report. If you continue, the price is the public list price on the pricing page: DCIM from $130 per node per year, hardware monitoring (ITOM) from $210 per node per year, annual subscription, no per-seat or per-socket counting. Volume tiers apply above 500 nodes.
If you stop, the VM is deleted and the credentials are revoked on your side. The pilot is free. There is no obligation to buy and no automatic conversion.
See pricingData Residency
The platform runs on your VM, inside your network. Hardware telemetry, metrics and configuration data stay there. Nothing is sent to Sensaka, to Mustard Seed Solutions or to any third party, during or after the pilot.
Sensaka is made by Mustard Seed Solutions sp. z o.o., registered in Warsaw, Poland, and subject to EU data protection law. Air-gapped environments are supported because there is nothing to connect to.
Security and data residencyPilot Questions
How long does the pilot take, and how much of my team's time?
Four weeks, free of charge. Expect two to three hours of your team's time in week one for network access, credentials and the VM, then roughly one hour a week for threshold reviews and the week-three drill. The final review is one meeting.
Does anything get installed on my servers?
No. Hardware monitoring in DCOS is agentless. It talks to the baseboard management controller of each server over IPMI, Redfish or SNMP. The only new software is the Sensaka platform on the one VM you provide.
Does any data leave my network?
No. Sensaka deploys on-premises. Hardware telemetry, metrics and configuration data stay inside your environment and are not transmitted to Sensaka, Mustard Seed Solutions or any third party. The platform does not phone home.
Which server vendors can the pilot cover?
Dell (iDRAC), HPE (iLO), Lenovo (XClarity), Huawei (iBMC), Supermicro and Cisco through IPMI and Redfish, plus SNMP-capable devices. Mixed estates are the normal case. Facility equipment such as UPS, cooling and PDUs can be added if you want DCIM in scope.
What does it cost after the pilot?
Public list prices are on the pricing page: the DCIM layer starts at $130 per node per year and hardware monitoring (ITOM) at $210 per node per year, billed annually. The pilot itself is free, with technical support from Sensaka engineering. There is no obligation to buy afterwards.
Who is behind Sensaka?
Sensaka is a product of Mustard Seed Solutions sp. z o.o., registered in Warsaw, Poland, an EU member state. The platform combines DCOS (hardware monitoring), iDCOS (ITSM and CMDB) and SmartBSM (AIOps), all deployed on-premises.
Ready to Scope a Pilot?
Send your approximate node count, server vendors and the outcome you need to prove. We reply with a one-page scope and a proposed week-one date. The pilot is free; Sensaka engineering supports it.