Matching and prioritisation
Pulls multiple official and public vulnerability sources, matches them to your asset versions and assigns one of four levels with the reasoning attached — or marks it "needs confirmation" when data is incomplete.
The AMAS family
Kaohsiung-born since 2015. Building AI that organisations can verify.
Corewatch matches official vulnerability feeds against the asset versions you actually run, every day. It prioritises by transparent rules, tracks remediation deadlines and turns every decision into audit evidence. Severity is decided by rules and version matching, never by AI.
Multi-tenant cloud service · two-step verification on every account
01 — The problem
For owners, security leads, engineers and auditors at IT service providers and growing businesses — every step from "does this affect us?" to "prove it is fixed" needs an owner and a record.
New CVEs land every day, but nobody maps them to the exact products and versions you run.
Gaps in the data get treated as safe, and real exposure drops off the list.
Remediation lives in emails and spreadsheets, rebuilt from scratch at every audit.
02 — Capabilities
All of the following are available today. Items marked "by plan" vary across the Free, Professional and Enterprise tiers.
Pulls multiple official and public vulnerability sources, matches them to your asset versions and assigns one of four levels with the reasoning attached — or marks it "needs confirmation" when data is incomplete.
Register assets by hand, collect host and container components, or upload SBOM and VEX statements.
Affected items open as tickets with response and resolution deadlines. Only people can mark an item patched or verified — with a note.
Email, LINE, Teams and webhooks, plus daily digests and product-watch alerts.
Monthly reports, deadline attainment and audit exports — plus a vendor-compliance document pack for public-sector contracts.
Export remediation tasks to your own AI agent and import its findings for a person to confirm. Read-only API tokens are available.
03 — How it works
Manually, via the collector, or by SBOM upload.
Daily official feeds, version matching and transparent rules — reasoning included.
Tickets by level, owners alerted, deadlines started.
People confirm the fix; the record exports straight to auditors.
04 — Governance & trust
Security records have to stand up to scrutiny, so who decided what must be unambiguous: rules set the level, people close the item.
Only rules and version matching. AI helps summarise official English advisories in Traditional Chinese — its output cannot change a level or a status.
Incomplete data is flagged for confirmation and stays on the list until someone resolves it.
Five roles with distinct duties, each organisation isolated from the others, and two-step verification on every account.
Every ticket, assignment, fix and verification is recorded and ready to export.
05 — Where it stands
The production service is live and used by our own organisation. External customer trials have not started yet; we can enable a Professional or Enterprise trial for organisations we are in conversation with. Self-service sign-up is not yet open.
Corewatch is cloud-only today; there is no on-premises edition.
Labelled by what is actually available; items not yet open cannot be ordered.
06 — The AMAS family
Each product runs on its own, and each keeps the same rules: clear roles, traceable records, and AI that assists but never decides.
Every answer cited. Every access governed.
Learn morePayroll calculated to Taiwan's rules, with maker-checker controls
Learn moreHours of footage, prioritised for human review
Learn moreNext step
Early-access enquiries: we walk through the full flow from vulnerability intelligence and version matching to remediation tracking and audit reports.