ForgeIQ¶
ForgeIQ is your interface to VirtualForge — where you sign in, set up your organization, configure what you own, and reach the connectors, tools, and intelligence you are entitled to.
It is the VirtualForge portal: the web application through which a customer meets the platform. Not a dashboard bolted onto the side of it — the front door, and the place nearly everything self-service eventually happens.
It is not a product you buy. It is the interaction plane: how you reach what you have bought. That is why it sits in its own section here rather than in the products portfolio — nothing in ForgeIQ is a separate purchase.
Status: in active development. ForgeIQ is being built now, against a defined front-end architecture, and it has not been released. We will not give you a release date before we have one; it is TBD. The initial focus is deliberately narrow — basic user interactions, context, and connectors — so most of what this page describes is where ForgeIQ is going, not what you can log into today. Everything it will report on — connectors, tools, ForgeVault — is shipping already.
What you will do here¶
The full intended scope, so the shape of it is clear even while it is being built:
| Area | What it is for |
|---|---|
| Sign-in | Authenticating to VirtualForge — the front door, and the identity everything else attaches to |
| Your organization and account | Setting up and maintaining your organization, its users, and its details, rather than asking us to do it |
| Products and features | Seeing what you have, adding new products and features, and managing them as your estate grows |
| Identity and licensing | The entitlement and licensing details that govern what you can run — established and maintained in one authoritative place |
| Configuration | Configuring the VirtualForge assets and products in your domain, directly |
| Operations and status | What is running, what it last did, and whether it is healthy |
| Tools, analysis, and intelligence | Reaching the Tools you are entitled to, and the intelligence they produce |
The connecting idea is entitlement: ForgeIQ shows you what is yours, lets you configure it, and lets you extend it. What appears for you is a function of what your organization owns, not a menu everyone sees the same version of.
Where it starts¶
Connectors are the initial focus, and the reason is worth stating plainly rather than presenting a subset as the whole design: our go-to-market leads with connectors, so that is where real customers have real things to look at, configure, and be told about first. The initial release is scoped to basic user interactions, context, and connectors for the same reason — earning the right to build the rest by getting the first part genuinely useful.
So the connector story below is the sharp end of ForgeIQ, not its boundary. The rest of the table above follows it.
The connector problem it addresses first¶
A connector is infrastructure, and infrastructure has a specific failure mode: it works so quietly that nobody watches it, and then it stops working just as quietly.
Understanding how a connector is behaving currently means reaching the host it runs on and reading logs. That is fine for an engineer with access and awkward for everyone else — which typically includes the people who actually depend on the data being current. The person who notices first is usually an analyst wondering why a signal stopped updating, which is the most expensive possible way to find out.
The other half of the problem is that a growing estate has no single view. One connector on one agent is manageable by hand; six connectors across three sites is a spreadsheet somebody maintains badly.
What it provides for connectors¶
- Operating state at a glance — what is running, when it last ran, and whether it is healthy.
- Indexing activity — what was updated, how long it took, and what changed.
- Health and alerting — problems surfaced and notified rather than discovered later.
- One view across the estate — every connector and tool together, not one host at a time.
- Self-service access — visibility for the people who depend on the data, not only for whoever can reach the host.
The intent is that connector health becomes something you can see without special access, and that EEI's support team sees the same picture you do. That is what makes proactive support a real capability rather than a promise.
What you have in the meantime¶
Health visibility is not absent while ForgeIQ is being finished.
Our connectors already publish structured diagnostics, and connector run reporting can be surfaced inside Seeq as trendable monitoring data — so operators who cannot reach the agent host can still see how indexing is behaving. That ships today; see Connectors ++.
ForgeIQ consolidates that same information across every connector and tool, adds alerting, and gives it a home that is not inside one host application.
Related¶
- Connectors ++ — the diagnostics and in-Seeq monitoring available now, including the optional VirtualForge connection that connector management arrives over.
- VirtualForge — the platform ForgeIQ is the interface to, and the other ways to work with it.
- Products — the portfolio, and where each product stands.
- VirtualForge Toolbox — how Tools reach you inside Seeq, which is the other side of the same coin: ForgeIQ is the VirtualForge-side interface, the Toolbox is the in-host one.