CREAIM · Runtime Computing Platform

Compute Less.
Preserve the Result.

Runtime Computing is the common compute-control layer behind CREAIM products across defense, pharma, semiconductor, security, media, verification, legal, personal AI and robotics.

Runtime Computing · MetaCore · Quantum-Inspired Q-Core Research ↗

Runtime Core
MetaCore Capability Surface
VERIFIED
State Reduction
Reduce states that no longer need evaluation.
VERIFIED
Recursive MetaCore
Coordinate Runtime Spaces across boundaries.
VERIFIED
Recovery + Replay
Checkpoint and deterministically replay execution.
VERIFIED
Evidence Export
Preserve result hashes and claim boundaries.
VERIFIED
Hybrid Routing
Route to CPU / GPU / HPC / future QPU.
PARTIAL
Open Compute Status
RESEARCH FRONTIER · QCORE-R1B-06CLASSICAL CPU RESEARCH · R1B-06 PASSSPEEDUP / PHYSICAL QPU: NOT VERIFIED

Quantum-Inspired Q-Core

Complex-Amplitude State Optimization Research

Runtime Computing and MetaCore provide the execution and evidence architecture. Q-Core explores interference-inspired selection of classical computational states for constrained optimization, including QUBO and MaxCut.

Research methodology and limitations

State / Candidate / Evidence

Research architecture: State → constraints → Q-Core candidate search → independent objective check → evidence.

22Exact benchmark problems
4,992Audited run records
466/466Node regression tests
0Physical QPU runs

Research validated on a single classical CPU environment. No physical QPU, quantum advantage, production integration or superiority over classical baselines is proven.

QCORE-R1B-06-06 · Internal same-host audit · Research PASS / Superiority HOLD / Production integration HOLD

RESEARCH CHALLENGE · 2026 · LOCAL EVIDENCE

Benchmark research, including evidence and limitations.

VRPTW local results: 10 checked seeds, 3 reproducible fixed-work runs and 23 local file checks. Not an official submission.

CREAIM PRODUCT UNIVERSE

One Runtime. Multiple real products.

CREAIM products are not disconnected projects. They extend a shared Runtime Computing and MetaCore layer into domain-specific runtimes.

Explore all products
One Runtime Core

Runtime Computing, MetaCore, Runtime Space and Evidence form the common compute-control layer behind CREAIM products.

Runtime ComputingMetaCoreRuntime SpaceExecution ControlEvidence
Status labels describe current technology/product maturity and do not by themselves imply customer adoption or public production deployment.
EXTERNAL PUBLIC BENCHMARK
5 / 5

5 / 5 submitted instances passed QOBLIB official CI validation.

External public benchmark evidence: two different optimization problem families, checked outside CREAIM’s own demo environment.

Open full evidence
WHY IT MATTERS

This is not an internal toy example. It asks whether CREAIM results pass an externally defined public benchmark, its instances, and its checker.

5/5
CI PASS
#84
3/3
#85
2/2
QOBLIB PR #84 · 07-independentset

Maximum Independent Set

OPEN · NOT MERGED · REVIEW
WHAT IS THE PROBLEM?

Given a graph, find the largest set of vertices such that no two selected vertices share an edge.

WHY IS IT HARD?

The number of possible selections grows combinatorially. QOBLIB uses unweighted MIS as one of its external optimization benchmark classes.

WHAT IT MEANS FOR CREAIM

This tests whether CREAIM can produce valid benchmark solutions under an external problem definition and checker, rather than only on an internal demo.

SUBMITTED INSTANCES
3 / 3 PASS
OFFICIAL CHECKER
OVERALL OK
C125-9 · result 34 · QOBLIB-listed optimal
p_hat1500-3 · result 94 · QOBLIB-listed optimal
hamming10-4 · result 40 · published best-known
QOBLIB PR #85 · 02-labs

LABS

Low Autocorrelation Binary Sequences
OPEN · NOT MERGED · REVIEW
WHAT IS THE PROBLEM?

Find a ±1 binary sequence that minimizes the sum of squared off-peak autocorrelations.

WHY IS IT HARD?

Changing one bit can affect many correlation terms at once, creating a difficult discrete search landscape.

WHAT IT MEANS FOR CREAIM

It provides a second, structurally different public benchmark family for checking CREAIM results with an external official CI pipeline.

SUBMITTED INSTANCES
2 / 2 PASS
OFFICIAL CHECKER
OVERALL OK
labs067 · energy 241 · published best-known
labs099 · energy 577 · published best-known
Classical execution only. CI validation is not PR acceptance or merge, does not independently prove optimality, and does not claim quantum advantage, new public best, or universal solver superiority.
Why Runtime

Change what needs to be computed.

More hardware is not the only answer.

Runtime Computing organizes problems into computational spaces, reduces unnecessary states, preserves valid work and routes remaining computation to an appropriate executor.

Understand Why Runtime
01 · SCALE HARDWARE

Add more hardware

Scale the resources used to evaluate the problem.

02 · CONTROL COMPUTE

Control the computation

Structure and reduce the work before consuming more compute, while preserving result semantics.

COMPUTE CONTROL FLOW

The Runtime layer sits before more compute is consumed.

INPUT
RUNTIME SPACES
REDUCE / PRESERVE / REUSE
METACORE
EXECUTOR
CPU · GPU · HPC · QPU
RESULT
EVIDENCE

State Reduction

Reduce states that no longer need evaluation while preserving result semantics.

Recursive MetaCore

Coordinate Runtime Spaces, scheduling and state movement across execution boundaries.

Recovery + Replay

Checkpoint, recover and deterministically replay verified execution.

Evidence

Preserve result hashes, runtime identity, execution metrics and claim boundaries.

Quantum Runtime

Runtime before QPU.

Reduce work classically and explore routing residual Runtime Spaces through a hybrid executor architecture.

Physical QPU execution and quantum advantage are not verified. Simulation remains classical computation.

Quantum Runtime
HYBRID ROUTING CONCEPT
01
Large Problem
02
Runtime Space
03
Classical Reduction
04
MetaCore Routing
05
CPU / GPU / Future QPU
06
Result + Evidence
Runtime API

Connect your workload to Runtime.

Submit asynchronous jobs, track execution and retain result and evidence hashes through the Runtime API.

API Docs
# Submit a runtime job
curl -X POST https://creaim-runtime-core.base44.app/functions/runtime-api-submit \
  -H "Authorization: Bearer $CREAIM_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "problem_type": "portfolio",
    "execution_mode": "cpu_exact",
    "runtime_profile": "adaptive",
    "evidence_level": "full",
    "input_url": "https://example.com/portfolio.json"
  }'

# Poll job status + evidence
curl https://creaim-runtime-core.base44.app/functions/runtime-api-get \
  -H "Authorization: Bearer $CREAIM_API_KEY" \
  -G --data-urlencode "job_id=job_01HZEXAMPLE"
Runtime Access

Runtime access for builders and organizations.

Explore public evidence, developer access and organization deployment options. Paid checkout remains PREP_READY until production billing is configured.

Research
Public evidence access
Free
• Public evidence records
• Claim boundaries
• Runtime Computing overview
• Research archive access
Developer
Individual builders
Pay-as-you-go
• Runtime API access
• CPU exact + heuristic execution
• Evidence export
• Community support
Pro
Professional teams
Contact
• Higher quotas
• Multiprocess runtime profile
• Priority queue
• Email support
Organization
Companies
Contact
• Organization billing
• Team management
• Shared evidence records
• SLA options
Government
Government & mission-critical
Contract
• Contract-based deployment
• On-prem runtime options
• Compliance support
• Dedicated channel