We build boundless systems on a bounded planet.
Autonomous energy, planet-agnostic architecture, continuous resource flow — three disciplines, one lab, already shipping.
- Energy
- Space
- Continuity
Infinity is not scale.It is the right continuity.
Not promise. Measure.
04 / 04
99.97%
12-month combined uptime — Mail · Cloud · Jacpol
40+
Enterprise customers in production
10 years
From lab to production — since 2016
ISO + CMMI
Process certification — 2026 target
Organizations we work with
All metrics from production, updated monthly.
live
Mission timeline
T−10y · T+0
A lab bench. November. A 3D printer kit, opened. Then: our own printers. Then: ceramic. Then: pastry. Then: recyclable plastic from sugar molasses. One question, asked through four shifts: if the resource is bounded, how can the system be boundless?
Hardware is captive to physics. Software writes the physics. That year, the focus shifted: from materials to software. IT, DevOps, consultancy. A stack hardened in production; open-sourced piece by piece along the way. Same question. New stage.
Ten years later. Same bench, different matter. In production today: an end-to-end cloud platform, an enterprise email server, ISO and CMMI alignment. Cloud services under one roof. Same question. The answer, in the stack.
03 / 03 logged
Three pillars. One question.
How do you build boundless systems on a bounded planet?
Energy
Bounded resource,
Boundless flow.
Not generating — managing. Not distributing — directing. Not consuming — measuring. One software from building to city. Autonomous decisions. AI works not to consume energy, but to make its flow boundless.
Space
Bounded world,
Boundless horizon.
Every line of code we write is designed to run on the Moon, on Mars. Not metaphor — architectural decision. Resources scarce. Latency high. Connection intermittent. Decisions autonomous. A system that lives under those constraints lives better on Earth too.
Continuity
Bounded matter,
Boundless use.
The linear economy is dead. Produce-consume-discard breaks physics. Energy, data, hardware, compute. Each must have a second, third, fourth life. The planet is bounded; the lifetimes of a resource are not.
Architecture
06 layers · v0.3
The same stack, running under every product.
Six layers, one diagram. Every product is born here, lives here, watched here.
RUBIKLABS Stack — v0.3
Compute
Kubernetes compute under every shipping service. Scheduled across dedicated and shared pools.
Object storage
Residency controls, immutable snapshots, version rollback.
Managed databases
Managed Postgres and Redis. Automated backups, point-in-time recovery, read replicas.
CI/CD
Rollout engine for every service. Blue/green, canary, error-rate gated rollback.
Observability
Unified logs, metrics, and traces. One query surface, shared instrumentation.
24×7 IT
On-call rotation and incident response for every service on the stack.
Stack v0.3 — currently in production. Every release ships with open-sourced pieces.
06 / 06 · in production
The portfolio
Mail is live. Cloud is on the way.
Portfolio status
release · v0.3.0
Nominal
- 01
Mail
Lead productSecure corporate email for institutions.
- Zero-access
- KVKK · GDPR
- Multi-tenant
- Built in Rust
LiveLive since 2026 - 02
Cloud
End-to-end cloud, running under every product.
- Kubernetes
- Managed databases
- On-call included
- Internal today
SoonIn development - 03
Jacpol
Authorization for NestJS — a package family, open-sourced from production.
- Open source · MIT
- NestJS
- 3 packages
- Kysely + Prisma
LiveLive since 2024
Last sync · now
Cases
03 / 03
Three customers. Three problems. Three outcomes.
The real story of systems in production. Names available on request.
- 01Insurance · Finance
~500 employees, multi-branch
Used
- Cloud
A failed KDPR audit: corporate correspondence was stored with an offshore provider.
Eight weeks to migrate to Mail. Zero-access architecture, multi-tenant deployment.
Six months later: all email traffic in Türkiye. KDPR audit clean. IT security report closed with a "full compliance" note.
Key metrics
8 weeks migration · 0 leaks · KVKK clean
- 02Software · SaaS
~30 employees, $1M+ ARR
Used
- Cloud
- 24×7 IT
30% annual bill increase from an offshore cloud provider. The "your data stays in Türkiye" promise to local customers couldn't hold.
Six weeks to migrate to Cloud. Kubernetes, managed Postgres, on-call included.
One year later: 40% bill reduction. p95 latency 35ms → 8ms. In production without a DevOps team of their own.
Key metrics
6 weeks migration · −40% bill · p95: 35ms → 8ms
- 03E-commerce · Retail
Hundreds of thousands of orders daily; 10× during campaigns
Used
- Cloud
- 24×7 IT
- Observability
A 10× traffic surge on Black Friday. The existing stack had taken four hours of downtime, two consecutive years.
Migrated to Cloud. Blue/green + canary deployments, 24×7 IT on-call.
The next Black Friday: 99.99% uptime, zero incidents, p95 stable. Orders up 23%.
Key metrics
4h downtime → 0 incidents · 99.99% uptime · orders +23%
For case details, customer references, and technical architecture, get in touch.
See case details →Operating doctrine
04 / 04
How we work
Four rules — written down, referred to, broken only with reason.
- 01I
We run what we ship.
Every line we ship runs on infrastructure we operate. No handoff after deploy. No on-call outsourced. Code, platform, runtime. One team, one accountability. The page goes off at 3 a.m. — the engineer who picks it up wrote the line. Ownership isn't bolted on at the end; it's carved in at the start.
- 02II
Open source is proof, not pitch.
We don't open-source ideas. We open-source what shipped, what survived its first incident, what hardened in production. The npm packages — Jacpol family and Netgsm Client — aren't a mission statement; they are a track record. We work it first. The world, second.
- 03III
One platform, many products.
Every product inherits the same compute, the same observability, the same on-call, the same deploy pipeline. When a product diverges, we write down why — and plan its return. Drift is not accidental; it is deliberate and temporary. The platform is a product too — the team uses it, the team improves it, the team measures it. The only difference is we do not sell it.
- 04IV
Bounded planet. Boundless systems.
Hardware is finite. Energy is finite. Attention is finite. We design every system as if the constraint were already there. Because it is — just not always visible on a dashboard. The thesis isn't aspirational; it's a filter. Before every architectural call, the same question: can this run, forever, on what we have? No → we don't build it. Unknown → we measure.
Team
03 / 03
The owners behind "we run what we ship."
A small engineering team in Eskişehir. The same people who write the code, ship the code, and pick up the page when it goes off at 3 a.m.
[name pending]
Founder, CTO
- Software
- Systems architecture
- DevOps
From hardware to software. The architect of the journey that began with a 3D printer kit in 2016. Behind ISO/CMMI alignment and the end-to-end cloud design.
[name pending]
Engineering Lead
- Backend
- NestJS
- Kubernetes
The verifier of every line in production. Behind the technical architecture of the Jacpol package family and the Cloud platform.
[name pending]
Operations Lead
- SRE
- On-call
- Observability
The voice of 24×7 IT. The engineer who closes Black Fridays with zero incidents and still picks up the page at 3 a.m.
The next card could be yours.
Open roles →You are next.
One call. Your problem, your scale, your constraint. A proposal within a week.