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
10 years
From lab to production — since 2016
3 products
In production today — Mail · Jacpol · Netgsm client
Open source
Jacpol and the Netgsm client — opened from production
ISO + CMMI
Process certification — 2026 target
Verifiable records. Details on request.
on record
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
4 layers · v0.3
Which layer provides which capability.
Not the order we build in — that is the roadmap. This is the stack that stands today: Cloud at the base, email and identity on top of it, development tools above that, and the products at the top.
Products
Mail, Cloud, the open-source modules — and the no-code products this platform is planned to host. Everything below exists to make these possible.
Development tools
SDKs, frameworks, and the planned no-code interface. The layer a product owner builds on — with code, or without it.
Email & identity
Email, SSO (OpenID Connect), SCIM provisioning and identity — capabilities every product inherits rather than rebuilds.
Cloud
The infrastructure everything runs on:
- Compute
- Object storage
- Managed databases
- CI/CD
- Observability
- 24×7 IT
SSO and OpenID Connect appear here as architectural components — not finished integrations or sales-ready features.
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.
- Encrypted at rest
- 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
Strategic direction
04 / 04
From corporate email to physical production.
One question, four stages. Each stage lays the ground for the next — status is shown, not promised.
- 01Live · evolving
Corporate email
A secure corporate email service, in production and in daily use today. Development continues to deepen its feature set for demanding institutional use.
- 02Next stage
Cloud provider
The cloud layer every product already runs on — internal today, opening to external teams as the next stage.
- 03Planned
No-code platform
Tools for a domain expert to build their own product without writing code, on infrastructure we run and operate.
- 04Long-term goal
Mobile factories
Mobile production systems that turn raw material into parts and building components — working together toward city-scale construction.
Only the first stage is in production today. The rest are honest direction, not availability.
1 / 4 live
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
01 / 01
The person behind "we run what we ship."
Founder-led, based in Eskişehir. The same hands that write the code, ship it, and pick up the page when it goes off at 3 a.m. The team is growing.
Halil Safa Sağlık
Founder & Tech Director
- Software
- Systems architecture
- DevOps
Halil leads engineering and infrastructure at RUBIKLABS. He is responsible for the holding architecture under which each product operates as a separate company.
Team is growing
The next name here could be yours.
We hire engineers who own a surface end-to-end — design, code, SLO, on-call. No handoffs, no committees.
Open roles →You are next.
One call. Your problem, your scale, your constraint. A proposal within a week.