4SODEEP TECH
FAENAR
Find a product
The 4SO product family on one foundation, with 4SO Lab at the centre.

4SO · DEEP TECH INFRASTRUCTURE COMPANY

Infrastructure that remains operable.

4SO turns hard infrastructure problems—state, failure, recovery, networking, data and lifecycle—into explicit product workflows. We build for Day‑2 operations, not only installation.

Explore products →How 4SO engineers systems →

The 4SO product family: three domains around 4SO Lab

  1. 1Platform FactoryBuild and operate RKE2, OKD and existing Kubernetes platforms.
  2. 2WorkspaceSecure browser workspaces and RDP/VNC/SSH access.
  3. 3Enterprise WordPressWordPress as a managed platform resource.
  4. 4DBaaS EnterpriseLifecycle for ten database engines, from MySQL and PostgreSQL to MongoDB and Qdrant.
  5. 5GeoDNSAuthoritative DNS and traffic management with an independent query path.
  6. 6Mail GatewayOutbound delivery, inbound protection and mail-node lifecycle.
  7. 74SO NetworkA network source of truth with provenance and confidence.
  8. 84SO LabThe shared method for researching, designing, building and verifying every product.
Infrastructure softwareDistributed systemsApplied AI with authority boundaries
00DEEP TECH COMPANY

About 4SO

Deep Tech is not a label for us;
it describes the class of problems we solve.

4SO builds infrastructure products whose value comes from deep engineering across system state, networks, storage, databases, security, failure movement, recovery and automation.

We put that complexity behind a coherent product experience so technical teams can operate outcomes instead of holding together unrelated tools.

01INFRASTRUCTURE SOFTWARE

Infrastructure as a product system

Control Plane, Data Plane, API, agents, installer and runtime are designed as one operational system.

02DISTRIBUTED SYSTEMS

Designed for failure

State, idempotency, quorum, failover, resume and recovery are normal product behavior.

03DATA & NETWORK

Data and network are the problem domain

Database lifecycle, authoritative DNS and network source-of-truth mechanics are first-class product concerns.

04APPLIED AI

AI inside an engineering boundary

AI accelerates analysis and implementation, while authorization and operational truth remain product-owned.

Infrastructure Software×Distributed Systems×Applied AI×Operational Discipline
4SO technology domains →
01PROBLEM FRAMING

Why 4SO

Infrastructure is more than installation.

Day‑1 matters, but operational cost and risk begin on Day‑2: capacity change, failure, upgrade, recovery, access and observability. When those paths are scattered across tools and individual memory, reliability becomes a people dependency.

01

Operational complexity

High availability, replication, backup, recovery, routing and policy each have their own mechanics. Keeping them correct together is an operational systems problem, not a software-install task.

02

Dependency on individual expertise

If the safe path exists only in one DBA, SysAdmin or SRE's memory, repeatability, handoff and recovery become fragile under pressure.

03

Change risk

Scale, upgrade and failover can become the incident when they run without admission checks, bounded execution and authoritative post-change verification.

04

Fragmented operating experience

Panel, API, automation and AI-assisted tools must operate on one resource and state model rather than presenting conflicting versions of service truth.

SHARED OUTCOMEA repeatable, traceable infrastructure lifecycle with less dependence on tribal memory and more evidence from the running system.

Products

Each product owns one clear responsibility.

From platform construction to databases, DNS, mail and secure workspaces, every 4SO product owns a concrete operational domain and carries it from initial deployment through Day‑2 operations.

All 4SO products →
DOMAIN 01Platforms and executionPLATFORM & RUNTIME
01

4SO Platform Factory

PRIVATE PLATFORM FACTORY
KubernetesPrivate CloudFleet Lifecycle

Turns raw servers or existing clusters into standardized Kubernetes and private-cloud platforms, then keeps build, import, upgrade, recovery and fleet lifecycle under one product boundary.

Technical detail →
02

4SO Workspace

SECURE WORKSPACE DELIVERY
Isolated SessionsRDP / VNC / SSHZero Client Footprint

Delivers browser workspaces and RDP/VNC/SSH access while keeping policy, data controls and execution separated from the user endpoint.

Technical detail →
03

Enterprise WordPress

MANAGED WORDPRESS PLATFORM
Self-hostedIdentity & SSOAutomated Backup

Treats WordPress as a managed platform resource, bringing identity, capacity, data/cache, edge, observability, backup and recovery into one self-hosted lifecycle.

Technical detail →
DOMAIN 02Data, DNS and communicationsDATA & COMMUNICATIONS
04

DBaaS Enterprise

DATABASE LIFECYCLE CONTROL PLANE
10 database enginesQuorum & HAStable Endpoint

Operates ten database engines (MySQL, PostgreSQL, Redis OSS, Valkey, MariaDB, MongoDB, ClickHouse, OpenSearch, ScyllaDB and Qdrant) as managed services with engine-native topologies, engine-native HA semantics, backup/restore, upgrade and stable endpoints.

Technical detail →
05

4SO GeoDNS

AUTHORITATIVE DNS & TRAFFIC
Authoritative DNSDNSSECMulti-region Traffic

Operates authoritative DNS and multi-region traffic through revisioned change, controlled delivery, DNSSEC and node lifecycle while keeping the DNS query path independent from a live control plane.

Technical detail →
06

4SO Mail Gateway

MAIL PLATFORM & GATEWAY
Multi-tenantPolicy & GateQueue & Delivery

Self-hosted mail platform for high-volume outbound delivery and protected inbound flow with tenant operations, access control, queue visibility and explicit mail-node lifecycle.

Technical detail →
DOMAIN 03Network intelligenceNETWORK INTELLIGENCE
07

4SO Network

NETWORK SOURCE OF TRUTH
Network SOTL2 · L3 ModelData Provenance

Transforms inventory, topology and configuration evidence into an analyzable model while keeping observed facts separate from inference and preserving provenance and confidence.

Technical detail →
02OPERATING MODEL

Operating model

One path from request to verified outcome.

Across operational 4SO products, an operator may start from the panel, Product API or an AI-assisted interface, but mutation follows one controlled path: persist intent, validate preconditions, execute through the owner layer and read the result back from the real runtime.

HUMANOperator ConsoleHuman experience and operator decision
APIProduct APIOne contract for automation
ASSISTAI-assisted OperationsAnalysis and planning without a bypass path
01
Product Control PlaneKeeps request, access and desired state inside one product-owned boundary.
02
Durable OperationsLong-running work has durable state, survives interruption and remains traceable.
03
Policy · Validation · EvidenceAuthorization, preconditions, topology and result are checked before and after mutation.
RUNTIME / DATA PLANETarget systemThe change is applied to the system that must serve the workload and the result is read back from that same system.
01

AI does not receive a separate mutation path for sensitive actions.

02

Request acceptance and operation success are different states.

03

Where the Data Plane is independent, Control Plane is not in the serving path.

04

Missing evidence remains unknown; the product must not manufacture a healthy state.

Lifecycle

From preflight to observation, one repeatable operating path.

LIFECYCLE OPERATIONS
01PreflightPRECONDITIONS
02ProvisionCREATE
03ValidateVERIFY
04OperateDAY‑2
05ScaleCAPACITY
06UpgradeCHANGE
07RecoverFAILURE
08ObserveRUNTIME
034SO LAB

4SO Lab

20 years of operational experience × AI × engineering discipline.

Experience × AI × Engineering Discipline

4SO Lab is the shared product-engineering method behind the portfolio. Human judgment frames the problem, automation and AI accelerate the work, and independent verification decides what can be trusted.

  1. 01Human experience defines the problem, constraints and real operational effect.
  2. 02AI and automation help analyze, implement and test without bypassing product controls.
  3. 03Every result is checked again against evidence, tests and observed runtime state.
4SO Lab engineering loop from problem framing through build and verification
What looks correct in source must still be proven in the running system.
4SO Lab engineering method →
04NETWORK INTELLIGENCE

Network Intelligence

From scattered network evidence to a model you can reason about.

4SO Network turns inventory, topology and configuration sources into a machine-readable model while preserving the distinction between observed facts and inferred relationships.

01 / INVENTORYInventory and normalizationNormalize heterogeneous sources into consistent machine-readable records.
02 / RELATIONSHIPSRelations and topologyModel connections without turning inference into unquestioned fact.
03 / L2 · L3Network modelStructured Layer-2, Layer-3 and routing domains for later analysis.
04 / PROVENANCEProvenance and confidenceKeep source identity and confidence attached to each derived view.

4SO vision

Introduce the infrastructure.
Choose the objective.
Operate the lifecycle.

Installation should not be the end of the product. The same system should guide capacity change, upgrade, failure, recovery and observation.

Deploy in your environmentScale through explicit workflowsTraceable recoveryConsistent operations
Explore 4SO products →
4SO contact platform: a globe of conversation paths above one plinth.
Phone0942 200 1122Email[email protected]