Each is its own product with its own page, inputs and reports. Start with the one that matches the state of your software.
Product
CORE Evaluate
Know exactly what you have, before anything changes.
Quality and testing across functional, regression, API, load, browser and device, accessibility and security. Compliance readiness against SOC 2, HIPAA, FedRAMP 20x, FISMA, NIST CSF 2.0 and CCPA/CPRA, with the file and line behind every verdict.
Works on code CORE did not write
Choose the tests; CORE asks only for what they need
Documents, screenshots and recorded calls in. A finished, tested system out, approved stage by stage: understanding, use cases, mock website, database, APIs, project.
Nothing generated until your people verify the design
Tested before handover
Standard source code in your repository, no runtime dependency
Testing and compliance reviews show what is wrong, where, and how much it matters.
Optimize and Re-engineer fix
Findings become approved changes, or a rebuild when the architecture is the problem.
Evaluate proves
The same tests and controls re-run, so improvement is shown, not asserted.
Self-heal runs in every product.
Supported vulnerabilities and compliance gaps fixed automatically, tests that repair themselves, parity differences corrected before handover. Every fix re-tested and recorded, and your team approves every step.
Choosing a product
Which CORE product should we start with?
Match it to the state of your software. If it runs but you are unsure of its quality or compliance, start with Evaluate. If it runs and needs to change, Optimize. If the technology or architecture is the problem, Re-engineer. If it does not exist yet, Create.
Where does rewriting a legacy application to a new stack belong?
In Re-engineer. Rewrites and re-architectures both start by recovering the business rules from the existing code, then prove the new system behaves the same way.
Can we use more than one product?
Yes. They share one engine, so findings from Evaluate flow into Optimize or Re-engineer, and Evaluate re-runs afterwards to prove the improvement.