global infrastructure holding · Spain

Continent-scale infrastructure — from the first commit.

Continentix is not a product. It is the structure under which products are built to survive continental scale: from one engineer to millions of users, from one server to global infrastructure.

What Continentix is

We do not chase launch counts. Ideas are sifted as strictly as code — only what has passed an audit, held under load, been restored from backup, and can withstand outside scrutiny earns the Continentix name.

01

One engineer, full accountability

Every product is designed, built, and operated by a single engineer. Every decision has an author; every line has an owner. Nothing is left to "later".

02

Primitives outlive products

Positioning dies in months; primitives hold value for years. We inventory molecules — signatures, attestation, trust thresholds, immutable logs, deterministic replay — and reuse them across products.

03

Scale is independence from geography

A Continentix product must work the same for one city and for a continent. That is the difference between a startup and infrastructure.

What we believe

Five principles. None of them is a slogan — each one maps to a rule enforced in code review and CI.

Security is the foundation

No home-grown cryptography. Standardised primitives only — ML-KEM, Ed25519, P-256, AES-GCM, Argon2id. Every protection claim names the attack class it defends against.

Architecture, not patches

Explicit responsibility boundaries, reproducible environments, local == production down to the engine version. Temporary fixes do not exist — only a found root cause or an open task.

Honesty over presentation

A risk is called a risk. Weak decisions are surfaced and fixed before release, not after user complaints. "Done" means verified end-to-end.

Autonomy is responsibility

Each product is designed as if it had to be defended tomorrow before a security board, an investor, and a user — at the same time.

Clean intellectual property

Permissive-licensed dependencies only, recorded in an SBOM; human authorship documented per file; copyleft contamination blocked in CI.

Principle, not promise

Every new project is checked against these principles — never the other way round. The manifesto changes only when practice changes, never to excuse a compromise.

The Continentix Standard

A system earns the name only after passing seven gates — each closed by a fact, not an intention.

1
Audit on diskNo plan without a written report of the real state of code and infrastructure.
2
Proven cryptographyStandardised primitives only; anything custom is an access scheme on top of them, with its threat model stated.
3
Clean IPEvery dependency permissive-licensed and in the SBOM; provenance of human authorship per file.
4
Environment parityLocal, test, and production run identical engine versions. No "faster test database".
5
Recovery proven by recoveryA backup that has never been restored is not a backup. The disaster procedure is written and rehearsed.
6
Separated planesControl never shares a path with customer traffic; critical actions require a second trusted device.
7
One change per cycleChanges land one at a time, each closed by verification.

What we build

Products different by nature, identical by standard — one foundation. Repositories move into the organisation one project at a time, each only after it passes the Standard.

VInfrastructure control

Valtrix

Secure infrastructure control plane: every destructive action waits for approval from a second device.

RustPostgreSQLFlutter
in developmentvaltrix.at ↗
DCommunication & keys

DevoraX2

Post-quantum, dual-device messenger with account recovery through a paired guardian device.

RustAxumFlutter
in developmentdevorax2.com ↗
SReady products

StartupProjects

Catalog of working products — website, back office, mobile app and store publishing. See it running, then order your own.

LaravelVue 3Flutter
VEngineering platform

Veltarra

AI-native visual engineering platform with a token-driven editor that generates framework code.

LaravelTypeScript
in developmentProject page coming soon
WOpen standard

Veltweave

Open standard for verifiable computed interfaces: one signed canonical graph, seven independent modes.

SpecificationMITCC BY 4.0
standardProject page coming soon
CVerifiable interfaces

Calcara

Deterministic replay for AI-assembled interfaces, rebuilt from a render receipt instead of a screen recording.

RustWeb SDK
blueprintProject page coming soon
ATrust primitive

Attesta

Cryptographic attestation primitive: a hash-chained black box reused across the portfolio.

RustMerkle proofs
primitiveProject page coming soon
SReliability

Sismara

Network seismograph: tells you whether a failing build is your change or a shared dependency down for everyone.

RustCLIAgent
blueprintProject page coming soon
PRegulated industries

Provata

KYC/AML verification for notaries, realtors, lawyers and gestorías, with a sealed, source-cited record of every check.

LaravelRust
blueprintProject page coming soon
RustAxumPostgreSQLLaravelVue 3FlutterProxmoxHetznerCloudflareOpenTelemetry

Contact

Partnerships, infrastructure work, or a security report — one address, one engineer answering.

Email
info@continentix.com
GitHub
github.com/Continentix
Security
Security policy & private reporting
Location
Spain · operating globally