Understand what you have and how it connects
Build the evidence-backed foundation Forge uses across every other workspace.
Use the areas on the left to discover, understand, protect, modernize, and operate your technology estate. Forge keeps simulated learning scenarios separate from customer evidence.
Each option in the left navigation has a specific purpose. Start anywhere, then move between workspaces as Forge learns more about your environment.
Build the evidence-backed foundation Forge uses across every other workspace.
Turn retained evidence into actionable operational and security intelligence.
Use Forge to accelerate engineering work while preserving architecture and operational context.
Teach Forge from approved sources and use evidence-aware reasoning across the estate.
Understand the service state and manage the customer relationship around the workspace.
Forge can demonstrate how a product may fit into an estate before customer evidence is connected.
Choose a vendor first. Forge will then show only products from that vendor in the second list. Loading a product creates an independent simulated estate for that specific technology.
Representative sample data generated for the selected technology.
Select any node to inspect representative evidence, ownership, and business impact.
Prioritized by business impact, technical risk, and evidence confidence.
A live, evidence-aware conversation about your technology estate.
Capture the architecture Forge needs before discovery, assessment, or modernization begins.
Operating system, Java runtime, and web tier
Select the technologies in scope, then capture product-specific details where applicable.
Database footprint, environments, and server scale
Custom code, plugins, workflows, and external dependencies
Select a vendor, choose one or more products, and add them to this environment.
Build a customer technology inventory across business platforms, infrastructure, security, data, and industry systems.
Collect authorized, read-only infrastructure evidence across public and private cloud providers.
| Name | Resource ID | Type | State | Private IP | Public IP |
|---|---|---|---|---|---|
| No cloud evidence loaded. | |||||
Select an observed environment and Forge will turn its evidence into a comprehensible architecture package.
Turn workload, platform, operational, and vendor-entitlement requirements into defensible engineering plans.
Forge will calculate an explainable planning baseline and show every assumption that affected the result.
The result includes topology, capacity, backup, security, validation, rollback, and a starter provisioning script.
Forge correlates host, runtime, application, dependency, network, and log evidence in one report.
| Vendor / product | Metric | Authorized | Observed | Peak | Assessment |
|---|
| Technology | Model / basis | Covered use | Attested by | Status | Action |
|---|---|---|---|---|---|
| No customer rights attestations loaded. | |||||
Review an entire local codebase for security, quality, efficiency, and cleanup opportunities.
The browser reads only the directory you choose. Nothing is sent to Forge Accelerant. Write access is requested separately—and only when you approve a safe cleanup.
Connect a local source directory to build the language and file inventory.
Forge will identify security risks, inefficient patterns, maintainability issues, debug code, and safe cleanup changes.
Describe what you want in everyday language. Forge teaches, builds, tests, and explains deployment one step at a time.
Collect logs and system evidence, identify likely causes, and create a prioritized recommendation report.
Choose a local directory. Forge reads supported text logs locally and looks for errors, exceptions, timeouts, SSL, authentication, database, and memory patterns.
Download the read-only Windows collector, run it on the workstation or server, then choose its ForgeDiagnostics output folder above.
Forge correlates timestamps and recurring signatures, then ranks recommendations by severity, confidence, and likely business effect.
Your selected files remain on this computer.
Connect a log or collector-output directory, then run the analysis.
Evidence-backed exposure, attack-path, control, and response intelligence across the business technology graph.
Forge correlates configuration, software inventory, identities, runtime connections, code, logs, vendor advisories, and business dependencies. Findings remain hypotheses until supported by retained evidence.
Search Forge-specific setup, administration, identity, discovery, Reasoner, training, deployment, and recovery guidance. Results are filtered by your company role.
Only guidance allowed for your authenticated company role is returned by the Forge API.
Tenant-scoped service operations for audit history, usage metering, discovery schedules, subscription state, and support.
One intelligence platform with Forge Reasoner available across managed SaaS, public cloud, private cloud, on-premises, Kubernetes, and OpenShift deployments.
Learn approved vendor documentation, retrieve evidence, and keep every AI answer traceable to its source.
Forge combines tenant-aware PostgreSQL knowledge with a curated OpenAI vector store. Customer evidence stays inside the Forge tenant boundary by default; the external store contains only globally reusable, approved knowledge.
Read-only listeners for on-premises, hybrid, private-cloud, and customer-cloud evidence — plus change intelligence across code, configuration, runtime, and business impact.
Use the listener ID and one-time secret above with the read-only collector for the target host. Evidence is sent outbound over HTTPS and lands in the shared Enterprise Model.
Forge does not stop at a CMDB record, source-code finding, telemetry signal, or architecture diagram. It connects all four, identifies contradictions, dates the evidence, and generates a reversible plan a first-time practitioner can follow.
Forge will trace source references, configuration, observed connections, technical services, business processes, and evidence conflicts.
Documentation creates hypotheses; customer configuration and runtime behavior prove or reject them.
Forge retains conflicting sources instead of silently choosing the most convenient answer.
Historical configuration, source references, owners, changes, and observed use form a technology timeline.
Every recommendation includes prerequisites, tests, approvals, deployment steps, and rollback instructions.