Everything the platform does — in plain answers.
What IntraLogic is, the areas it covers, how the AI assistant helps, what you can report on, and how security works — grouped by topic.
Simulation accuracy, what the assistant will not do, what the agent does not collect — the boundaries are stated in the answer rather than left to be discovered.
IntraLogic is in preview ahead of GA in Q1 2027, so every answer describes what is built today rather than what is planned.
What IntraLogic is.
Simulation computes dependency impact against your documented model — what depends on what, and what stops working if a component fails. Its accuracy depends on that model matching your environment.
It does not predict physical behaviour (thermal, electrical, timing, firmware defects or vendor-specific failover quirks), does not verify that redundancy configured on paper actually works, and does not replace vendor-recommended testing or confirm equipment is configured to manufacturer guidance. Treat a result as an informed expectation to verify, not a guarantee. Full detail →
An infrastructure intelligence and simulation platform. It turns documentation, integrations, and monitoring signals into one connected model of the environment that teams can simulate, report on, and version.
No — it complements monitoring. Monitoring tells you something is down; IntraLogic shows what it means by understanding dependencies and impact across the whole environment.
No. The model and its impact simulation run on explicit, auditable logic you can trust. AI is a rich helper layered on top — it never replaces the deterministic engine.
It removes blind troubleshooting. Teams start incidents from context instead of guesswork, and can see — or simulate — how a single failure spreads before it becomes a wider outage.
What parts of the environment are modeled.
Seven connected object types — Sites, Physical, Roles & Applications, Storage, Virtual, VDI and Backup — kept linked so impact is understood end to end rather than in silos.
Multi-site topology, ISP and connectivity paths, site dependencies, and business-continuity impact.
Racks, devices, switches, cabling, storage paths, and management IPs — the physical layer and its dependencies.
Two linked things. The core roles an environment quietly stands on — Active Directory and domain services, DNS, DHCP, identity, databases, brokers, file services. And the business applications people actually use, each mapped to the roles and workloads it depends on.
That second half is the point: it is where infrastructure stops being infrastructure and becomes “the practice-management system is down”. Because applications are modelled as objects in their own right rather than a label on a server, a failure anywhere beneath them resolves to the named applications at risk — which is the answer the business actually asked for.
Controllers, disks, vdevs, pools, redundancy, multipath, and degraded-state simulation.
Clusters, nodes, VMs, resource pressure, and virtualization failure scenarios.
Yes. A failure propagates across the chain — switch → host → VM → role → application — so you see full impact, not just the device that failed.
How the AI helps — and what it doesn’t do.
Three things: add objects by describing them, set up what-if tests in plain language, and answer questions about the live model — dependencies, impact, and findings — in context.
Yes. Upload CSV exports, PDFs, Visio diagrams, screenshots, images, and more — the system processes them and extracts the objects (sites, devices, roles, storage, VMs, and their relationships) into the model. Everything is presented for your review before it’s added.
No. The assistant is read-only and review-first. It proposes objects, tests, and answers, but nothing enters the model until you confirm.
No. The deterministic engine runs every simulation. The assistant just helps you set scenarios up and explains the results.
What you can export and share.
CSV, PDF, and interactive HTML — from any single module or the whole environment, in one consistent enterprise format.
Yes — on-demand email reports from any module, with scheduled delivery for client, site and health-score reports.
Inventory, dependencies, health scores, and alert snapshots — available per module (Sites, Physical, Roles, Storage, Virtual) or as a combined environment report.
How the platform stays safe to adopt.
Yes. Integrations are read-only by default, so adopting the platform never modifies your infrastructure. Detected changes are reviewed before they update the model.
Role-aware access scoped by organization, client, module, and responsibility — the same controls apply across every area of the product.
Yes — full audit logging captures who changed what, when, why, and from which source.
Published baselines can be compared over time, new discoveries are checked against the approved model before adoption, and alert snapshots are tied to the model version that existed at the time of the event.
How it’s packaged.
No unit is published yet. Pricing is being finalised ahead of general availability, so quoting a basis now — per site, per managed client, per device — would be a number we might have to take back. What is firm: you are told at least 30 days before any billing begins. What is settled so far →
Yes — by managed client, by service tier, or as an advanced documentation, simulation, and reporting add-on.
Yes. The same model works for small environments and scales into larger MSP and enterprise deployments as sites, roles, storage, and virtual infrastructure grow.