About

A data platform built by people who got paged for it.

rjbase.io started as an internal tool. After the fifth team asked us to ship it as a product, we agreed.

Our story

Tokenization, but for everyone’s data.

Most data infrastructure assumes the people running it can be trusted with everything inside it. That assumption breaks the moment your company sells to a regulated industry, signs a contract with a sovereign customer, or hires its hundredth analyst.

The founders of rjbase had spent a decade building lakes at FAANG-scale companies and finance shops, and each of those lakes had a homegrown tokenization layer bolted onto it. We thought: what if tokenization were the substrate, and the lake sat on top of it? That inversion is the whole company.

Principles

  • Default to opacity. If a column is not declared safe, treat it as sensitive.
  • Engine, not docs. If a policy is not enforced at plan time, it does not exist.
  • Every reveal has a name. No anonymous detokenization, ever.
  • Operate it before you ship it. We run the same code paths we sell.
Leadership

A small team that has done this before.

RW

R. Wong

Founder & CEO

Previously led the data platform team at a Fortune-50 retailer. Spent six years on payments compliance before that. PCI veteran.

JD

J. Delgado

Founder & CTO

Built the columnar engine at a public AdTech company. Contributor to several open table-format projects. Has strong opinions about Z-order indexes.

AP

A. Patel

Head of Security

Ran the offensive security team at a top-five US bank. Believes the best access policy is the one your attackers cannot reach in the first place.

Backing

Patient capital, not platform tax.

rjbase.io is funded by infrastructure-focused investors who have backed previous category-defining data platforms. We do not take revenue share on usage and we do not lock customers into proprietary file formats. The lake is yours; we just make it safer.

By the numbers

2023
Founded
38
Team
4
Regions
100%
Remote
Now in private preview

Tokenize your data. Keep your governance.

Talk to our team about an evaluation cluster. We typically have engineering partnerships running inside two weeks.