Research and web platform
Versioned research artefacts, Strata design tokens, semantic web pages, and reproducible validation gates.
Correctness under concurrency.
Pinega turns database-systems research into high-performance software across storage, transactions, optimisation, verification, and distributed execution. Pinega Engine is the first active implementation programme; it is not yet a production release.
Current programme status
Pinega Engine
An extension-oriented PostgreSQL OLTP architecture under design and implementation validation.
Optimisation, verification, and distributed systems
Research directions with explicit product potential, not shipped products or performance claims.
Programme thesis
Performance matters only when the result remains correct and explainable.
Pinega connects formal reasoning, systems experiments, production engineering, and commercial intent. The objective is reusable intellectual property and measurable customer value, not isolated demonstrations.
Correctness under concurrency
Histories, visibility, publication, lifetime protection, durability, and failure boundaries are explicit design objects.
Performance with evidence
Cache behaviour, NUMA placement, SIMD, storage media, and query planning are measured rather than advertised in advance.
Research to product
Papers and hypotheses move through models, verification, implementation, benchmarks, and documented product boundaries.
Technology programmes
One programme, several paths to defensible database software.
Programme labels describe active research and engineering boundaries. They do not imply commercial availability.
Pinega Engine
Version-first OLTP storage, a Pinega-owned shared buffer pool, PostgreSQL integration, and one PostgreSQL WAL boundary.
Inspect the engine programmeQuery optimisation and AI
Cardinality reasoning, query rewrites, MCTS/RL join ordering, and low-latency inference for future optimiser products.
Inspect the optimisation directionCorrectness and verification
Executable models, deterministic testing, semantic diagrams, and tools for validating concurrent and transactional systems.
Inspect the verification directionFeatured active programme
Pinega Engine: an explicit OLTP path inside PostgreSQL.
The current architecture separates PostgreSQL integration, mutable versions, shared-frame lifetimes, and durability. It is an accepted design direction under implementation validation, not an installable release.
-
01
PostgreSQL integrationTable AM callbacks, snapshots, transactions, and SQL-visible behaviourtarget
-
02
Mutable version storeOut-of-place tuples, stable handles, and explicit visibility metadatadesign
-
03
Shared buffer poolStable frames, protect/pin/revalidate, cache-aware placement, and reclamationresearch
-
04
PostgreSQL WALOne write-ahead log and one transaction durability boundarydecision
Research-to-product discipline
Claims advance only when their evidence advances.
Source and formalise
Start from papers, standards, source code, tests, and measured system behaviour. Keep external evidence separate from inference.
Prototype and falsify
Turn architectural ideas into executable models, focused prototypes, deterministic schedules, and benchmarks with explicit failure criteria.
Implement and productise
Promote only validated capability into maintained software, documented support boundaries, licensing, and customer-facing claims.
Maturity ledger
What exists, what is being validated, and what remains proposed.
| Area | Current state | Evidence boundary |
|---|---|---|
| YDMP research workspace | Available | Versioned notes, MODEL/VERIFY artefacts, build commands, and CI |
| Pinega Strata and Web platform | Available | Canonical tokens, Web Components, static pages, and browser/accessibility gates |
| Scientific Diagram Language | Available | Canonical models, Web/Typst renderers, layout profiles, and review artifacts |
| Pinega Engine architecture | Under validation | Accepted decisions and executable specimens; no production engine binary |
| Future product programmes | Research | No commercial availability or measured product claims yet |
Start with the boundary
Understand the programmes, then inspect the evidence.
Technology describes what Pinega is building; Research explains why; Documentation shows what can be reproduced today.