Your business, mapped.
Live relationships across technology, data, and business operations.
Observed technologies
27
8 reusable models readyRelationships
146
91 runtime verifiedBusiness processes
8
3 mission criticalOpen findings
11
2 need attentionSelected technology
HealthyPriority findings
Critical
Image Services blocks ICN upgrade path
98% confidence2 applications and 6.2M active documents affected
High
SQL17 has no verified failover route
94% confidenceClaims intake and reporting share one dependency
Medium
Three undocumented LDAP service accounts
87% confidenceOwnership not confirmed in the last 180 days
Evidence quality
92% groundedRuntime observations1,284
Configuration references438
Internal documents76
Vendor sources129
Unverified claims12
Technology graph
Select any node to inspect evidence, ownership, and business impact.
Claims ecosystem
Runtime viewEvidence inspector
HealthyFindings
Prioritized by business impact, technical risk, and evidence confidence.
✦
Ask Forge
Answers are grounded in your environment and show their evidence.
Critical impact
Do not shut down SQL17.
SQL17 supports the FileNet object store, Claims Reporting, and Billing API. Its loss would interrupt four business capabilities and document retrieval for approximately 4,800 users.
Business impact
Claims intake — processing stops
Customer portal — documents unavailable
Billing — API requests fail
Evidence · 97% confidence
3 observed JDBC connections
2 application configurations
Network flow verified today
Environment blueprint
Capture the architecture Forge needs before discovery, assessment, or modernization begins.
1
Platform foundation
Operating system, Java runtime, and web tier
Use a representative path; credentials are never requested.
2
FileNet platform
Product generation, release, and deployment model
3
Data and infrastructure
Database footprint, environments, and server scale
4
Customizations and integrations
Custom code, plugins, workflows, and external dependencies
Customization inventory
Select all customizations that applyOpen list ▾
Navigator and user experience
FileNet services and repository behavior
Applications, APIs, and authentication
Workflow, jobs, and operations
External integration inventory
Select every connected external systemOpen list ▾
Enterprise business platforms
Identity and security
Content, storage, and data
Messaging, transfer, and APIs
Reporting, monitoring, and scheduling
50 selected
IBM automation capabilities
Select installed add-ons and related CP4BA capabilities
Content, capture, and governance
Workflow, case, and application design
Decisions and operational intelligence
Archiving, integration, and task automation
Selections describe expected capabilities only. Forge will verify installed components, versions, and active dependencies during discovery.
Enterprise technology catalog
Build a customer technology inventory across business platforms, infrastructure, security, data, and industry systems.
Architecture document studio
Select an observed environment and Forge will turn its evidence into a comprehensible architecture package.
Infrastructure & capacity studio
Turn workload, platform, operational, and vendor-entitlement requirements into defensible engineering plans.
New environment or server
Workload modelPercentage of authorized users active simultaneously.
Capacity recommendation
Ready▤Enter the expected workload
Forge will calculate an explainable planning baseline and show every assumption that affected the result.
Database requirements
Build planForge generates a reviewable build plan and vendor-specific starter script. Production execution remains approval-gated and must use customer-controlled credentials.
Database build package
Waiting▱Describe the database workload
The result includes topology, capacity, backup, security, validation, rollback, and a starter provisioning script.
Metrics collection
Read only
Metrics to collect
Browsers cannot inspect remote servers directly. The production Forge Collector runs locally with read-only permissions and returns signed metrics to the selected tenant.
Application health report
Demo ready⌁Universal application metrics
Forge correlates host, runtime, application, dependency, network, and log evidence in one report.
Vendor entitlement
Customer suppliedForge compares quantities only when the observed measure matches the contractual license metric. It flags uncertainty instead of declaring compliance or overlicensing from incompatible evidence.
License position report
0Entitlements
0Need review
0Vendors
| Vendor / product | Metric | Authorized | Observed | Peak | Assessment |
|---|
Enter vendor-authorized quantities and observed usage to build an evidence-backed renewal, compliance, or rightsizing report.
Forge code review
Review an entire local codebase for security, quality, efficiency, and cleanup opportunities.
◉
Your source code stays on this computer.
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.
Source directory
No directory connected
JavaJavaScriptTypeScriptVB / VBScriptC#PythonC / C++GoRustPHPRubyKotlinSwiftScalaSQLPowerShellShellGroovyCOBOLHTML / CSS / XML
0Source files
0Languages
0Lines reviewed
0Findings
0Safe fixes
Project files
Waiting⌁No directory selected
Connect a local source directory to build the language and file inventory.
Review findings
Not started◇Ready for review
Forge will identify security risks, inefficient patterns, maintainability issues, debug code, and safe cleanup changes.
Forge development studio
Describe what you want in everyday language. Forge teaches, builds, tests, and explains deployment one step at a time.
Project conversation
Saved on this device so you can continue laterForge: Tell me what you want to build. You can write it exactly as you would explain it to a coworker. I will ask one question at a time, create the project plan, generate the code, help test it, and give you deployment instructions.
Build journey
1 of 5 active1
Understand the goalPurpose, users, security, and constraints
2
Design the solutionArchitecture and plain-language decisions
3
Build the codeFiles, configuration, and explanations
4
Test safelyAutomated checks and guided validation
5
Deploy and operateInstallation, rollback, and monitoring
Test lab
Safe browser sandboxReady. JavaScript and HTML run inside an isolated browser sandbox. Compiled languages receive structural and security validation until the secure build runner is connected.
Troubleshooting center
Collect logs and system evidence, identify likely causes, and create a prioritized recommendation report.
Evidence collection
Not started1
Application and server logs
Choose a local directory. Forge reads supported text logs locally and looks for errors, exceptions, timeouts, SSL, authentication, database, and memory patterns.
2
CPU, memory, network, and Windows Event Logs
Download the read-only Windows collector, run it on the workstation or server, then choose its ForgeDiagnostics output folder above.
3
Analyze and report
Forge correlates timestamps and recurring signatures, then ranks recommendations by severity, confidence, and likely business effect.
No evidence connected
Your selected files remain on this computer.
Diagnostic report
Report waiting for evidence
Connect a log or collector-output directory, then run the analysis.
Choose how Forge runs
One intelligence platform with managed SaaS, customer-cloud, and on-premises deployment options.
Start your Forge workspace
Forge Cloud SaaSProduct intelligence
Reusable technology models built from authoritative sources, then verified against each customer.
Learn another product
Research + environmentIdentify product and vendor Waiting
Analyze documentation and APIs Waiting
Match runtime evidence Waiting
Build product model Waiting
Validated in the claims lab
Environment evidenceIBM FileNet P8Architecture · configuration · logs · dependencies
99% confidenceIBM Content NavigatorPlugins · repositories · desktops · viewer stack
98% confidenceWebSphere Application ServerClusters · JVMs · certificates · data sources
97% confidenceMicrosoft SQL ServerInstances · databases · connections · failover
96% confidenceEnterprise knowledge models
Knowledge ready · customer environment not yet observed
Forge Edge
Technology archaeology and change intelligence across code, configuration, runtime, and business impact.
One proof chain from proposed change to business consequence.
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.
5 layersCode through business process
4 statesVerified, inferred, conflicting, stale
1 ledgerEvery conclusion carries proof
0 lock-inVendor and cloud neutral
Change request
Read-only simulationForge uses the goal to distinguish necessary dependencies from accidental ones.
Simulation never modifies the environment. Execution requires a reviewed plan, named approver, test evidence, and rollback checkpoint.
Cross-layer impact
Waiting◆Choose a change to investigate
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.