Repeatable benchmark
PostgreSQL reference workload
Five warm-cache runs, 41,884 measured requests, request-level JSON, resource observations, environment metadata, runner source, verifier, and SHA-256 checksums.
559.87 req/s median · 0 errors
Primary material
Core Panel research, raw results, and methods
This is the citable evidence behind Core Panel's measured claims. Each result identifies its scope, date, environment or source revision, method, raw artifacts, and limitations.
Evidence index updated September 20, 2026 · Machine-readable manifest
Migration measurement
Synthetic cPanel archive conversion fixture
Ten repeated conversions of a disclosed 20-entry synthetic full-account fixture at product revision 301a69f. This measures conversion-test execution, not customer migration time.
10/10 passed · 0.48s median
Security verification
Selected defensive-control regression tests
Developer-run checks for traversal rejection, recovery integrity, session tampering and expiry, size limits, filesystem failures, security-policy validation, and restore-drill evidence.
13/13 top-level tests passed
Not an independent audit or penetration test. Core Panel remains classified as pre-production.
Pricing history
Dated list-price ledger
Core Panel's single-server plan changed from US$6 to A$9 on September 3, 2026. The ledger records effective dates, currencies, billing units, repository revisions, and a dated cPanel Store snapshot.
Comparison methodology
How product claims are evaluated
The published method defines source hierarchy, pricing normalization, capability evidence, equivalent benchmark requirements, migration measurement fields, security evidence levels, and correction rules.
Read methodology version 1.0 →Evidence standard
- Identify: stable study ID, date, product revision, and maintainer.
- Reproduce: command, runner, fixture, environment, and configuration.
- Inspect: every run, failures, machine-readable summary, and checksum.
- Limit: state what the evidence does not establish.
- Correct: issue a versioned artifact instead of silently changing a result.
How to cite these materials
Name Core Panel Inc. as publisher, include the study or dataset ID, publication date, direct artifact URL, product revision where supplied, and access date. Cite the limitation statement beside any derived claim.
Core Panel Inc. (2026). “migration-fixture-2026-09-20.” Product revision 301a69f. Summary and raw Go test events. Accessed [date].