Release notes for the IntraLogic platform.
These notes track development milestones during IntraLogic’s preview, ahead of general availability in the first quarter of 2027 — feature enhancements, model updates, security improvements, and governance capabilities across versions.
Feature notes, UX refinements, integration updates, security improvements, and platform maturity.
Documented changes to infrastructure logic, simulation behavior, state snapshots, and rule interpretation.
Platform history
Expand any release to see what it introduced. Everything below is marked Preview: the platform is in preview until general availability in the first quarter of 2027, so nothing here is yet covered by a general-availability commitment.
Credentials and discovery settings become reusable objects owned by the client, instead of configuration trapped inside one agent.
- NewDefine a credential once and reuse it everywhere a discovery needs it.
- NewDiscovery profiles belong to the client, not the agent — so replacing an agent no longer means re-entering its configuration.
- NewAttach, copy, or clone a profile, with a duplicate guard and an audit trail behind each action.
- NewAn agents overview across every client, plus a per-client dashboard for the agents serving that client.
- ImprovedEnrollment tokens are scoped to a client.
- ImprovedDiscovery imports no longer have to run in a set order. Every import re-reconciles what is already in the model, so a datastore imported before its storage array, or a host before its switch, is folded onto the real object by identity as soon as that object arrives — rather than being stranded as a placeholder until someone re-runs the whole sequence.
Discovery configuration becomes part of the client’s record rather than a property of whichever agent happens to be installed.
One append-only event store now sits behind every activity surface in the platform.
- NewModel changes, agent actions, and assistant actions all record to the same feed.
- NewField-level change detection, so an entry says which value changed and what it changed from.
- NewOne correlation identifier per request ties an action to everything it caused.
- NewFailed sign-ins and agent security actions appear in that feed alongside everything else.
- ImprovedNinety days stay immediately searchable; older events are archived and remain searchable.
Answering “who changed this, and when” stops being a reconstruction.
Discovered infrastructure is correlated into one dependency graph, and every object gets a record page of its own.
- NewCross-domain correlation by MAC address and SCSI identity, so a device found by two connectors stays one object.
- NewEvery relationship records the evidence behind it.
- NewLow-confidence matches go to review rather than into the model.
- NewFull-page records for hosts, virtual machines, switches, and storage arrays.
- ImprovedThe graph is versioned, with compare and rollback.
- ImprovedSimulation follows discovered connections, not only the ones drawn by hand.
Every link in the model can be traced back to what was actually observed.
Read-only connectors collect what is actually running, and nothing enters the model without review.
- NewRead-only connectors across virtualization, storage, network, and hardware platforms — every one of them outbound-only.
- NewEverything discovered goes to a review step before it becomes part of the model.
- NewDiscovery runs on a schedule or on demand.
- NewDiscovered inventory is searchable, and the assistant can answer questions about it.
- ImprovedSSH is restricted to an allowlist of read-only commands, and running-config collection was removed entirely.
- ImprovedOne discovery can use more than one method against the same platform — a primary API call and an SSH supplement in the same run, for the parts one protocol can reach and the other cannot. Where two methods report the same field, a source policy decides which wins and records which one did, so a later run reconciles against it instead of overwriting it.
- ImprovedNow that discovery keeps the model moving, published client documentation is fingerprinted against it — a change to sites, racks, devices, virtual machines, storage, core roles, applications, backups or WAN links marks that document out of date and names what moved, rather than leaving it quietly wrong.
Scheduled discovery is new.
It accepts intervals from fifteen minutes to a week; cron expressions are not supported yet, and the scheduler has had no field soak. On-demand discovery is the well-travelled path.
Discovery narrows the gap between the documented model and the running environment.
Living, AI-generated client documentation — always current with the live model and fully version-controlled.
- NewGenerate client-facing documentation directly from the infrastructure model.
- NewVersion history so every revision is tracked, compared, and restorable.
- NewNarrative carry-forward preserves context across regenerations; edit details or raw HTML.
- NewPublished per client under a dedicated Documentation area.
Documentation stays in step with the environment instead of drifting out of date.
A release entirely about the front door. Security is a first-order concern here, not a section at the end of the deck — and the parts a security review reaches first are the parts worth documenting precisely.
- NewMulti-factor authentication, with two methods: a six-digit code sent by email, or an authenticator app using standard time-based one-time passwords.
- NewMFA is required by default and managed per user, with an enrolment grace window. Only a super administrator can exempt an account — a tenant administrator has no way to switch it off, for themselves or for anyone else.
- NewEvery sign-in attempt is recorded with its source IP and user agent, whether MFA was presented and whether it passed, which flow it came through — password, MFA, or password reset — and, when it failed, why.
- NewA self-service profile page: a user can review their own sign-in history, step up to MFA, and set a recovery address without raising a ticket.
- NewAccounts can be enabled and disabled, and the record keeps who disabled one and when.
- ImprovedPassword-reset links and emailed codes are single-use and time-limited, and are marked consumed the moment they are used.
- ImprovedAuthenticator secrets are encrypted at rest rather than stored in the clear.
None of this is a compliance claim — it is the account layer described plainly, so a security review can check it rather than take it on trust. What we cannot claim yet is on the trust centre, stated just as plainly.
An optional, outbound-only agent that checks your documented model against what's actually running.
- NewLightweight Windows agent (MSI) that collects read-only inventory and reports back securely.
- NewOutbound-only by design — no inbound ports and no agent-side control surface.
- NewCompares discovered reality against the documented model to surface drift and gaps.
- NewClient-scoped enrollment with credentials encrypted at rest and split agent / operational logging on short retention.
Closes the loop between documentation and live infrastructure.
Lifecycle tracking for every device — warranty, support, and end-of-life in one place.
- NewCapture purchase, warranty, support-contract, and end-of-life dates per device.
- NewAsset Management dashboard with filters and CSV, PDF, and HTML reports.
- NewAutomated expiration alerts so renewals and refreshes never slip.
- ImprovedLifecycle findings surfaced in the health score and dashboard widgets.
Hardware lifecycle becomes a managed, reportable part of the environment.
A rich AI assistant joins the platform — a helper layered on top of the engine. The model and simulation engine stay deterministic and auditable; the assistant does not replace them.
- NewAdd objects by describing them — sites, devices, roles, storage, and VMs drafted into the structured model for review.
- NewSet up what-if tests in plain language; the deterministic engine runs the simulation.
- NewAsk questions about the live model — dependencies, impact, and findings — and get answers in context.
- NewRead-only and review-first: the assistant proposes, you confirm before anything is published.
AI accelerates how the model is built and explored, without changing what the engine is.
Point-in-time versions of the environment model, with side-by-side comparison across approved baselines.
- NewCapture published versions of the model as the environment evolves.
- NewCompare any two versions to see exactly what changed and when.
- NewApprove official baselines your team works from.
- ImprovedVersion-aware reporting and audit evidence.
The platform becomes a system of record for how infrastructure changes over time.
Enterprise reporting now spans every module, with the export formats teams actually need.
- NewExport to CSV, PDF, and interactive HTML from any module or the whole environment.
- NewScheduled and on-demand email reports for stakeholders and leadership.
- ImprovedConsistent enterprise letterhead across inventory, dependencies, health scores, and alert snapshots.
- ImprovedPer-module reports for Sites, Physical, Roles, Storage, and Virtual — plus a combined environment report.
Reporting becomes a first-class capability across the entire product, not a single screen.
Controls for larger organizations and MSP environments.
- NewPer-organization, per-client, and per-module feature governance and toggles.
- NewAudit trail for reviewed changes, approvals, and generated reports.
- NewCompliance-ready evidence around model state, alert state, and operational decisions.
- ImprovedRole-aware access scoped by organization, client, and module.
The platform becomes a stronger system of record for how infrastructure is understood over time.
Connects existing documentation sources with the IntraLogic model.
- NewIngestion of uploaded reference material — CSV, PDF, Visio and screenshots — extracted into the model for review.
- NewClarification prompts when documentation is incomplete, conflicting, or ambiguous.
- NewReviewed model publishing so teams approve the official environment view.
- ImprovedImproved cross-object logic across Sites, Physical, Roles, Storage, and Virtual.
Reduces the gap between written documentation and operational understanding.
Establishes the core IntraLogic structure and the connected model.
- NewSites Intelligence and multi-location environment representation.
- NewPhysical infrastructure views for devices, racks, paths, and dependencies.
- NewCore Roles mapping for identity, DNS, DHCP, applications, and supporting services.
- NewStorage and Virtual modules with baseline simulation and state visualization.
Sets the core principle: move from raw visibility to real infrastructure understanding.
Release notes support trust and operational control.
Customer Trust
Customers can review platform improvements and understand new operational capabilities.
Internal Control
Teams can track which version introduced each feature, rule change, or workflow improvement.
Governance
Release notes support change reviews, platform audits, and long-term operational accountability.