Today's Deep-Dive: OpenPCC
Ep. 404

Today's Deep-Dive: OpenPCC

Episode description

In this episode, we take a deep dive into OpenPCC, an open-source framework designed to make private, compliant AI inference possible without forcing organizations to hand sensitive data over to opaque cloud vendors. Starting with the idea that corporate data should be treated less like fuel and more like hazardous material, we explore why standard AI workflows create such serious privacy and compliance risks, and how OpenPCC offers a fundamentally different model built on verifiable privacy rather than trust.

Along the way, we unpack the core mechanics behind the system, from hardware attestation and secure enclaves to oblivious HTTP relays that separate who is asking from what is being asked. We also look at how services built on top of OpenPCC can offer an OpenAI-compatible developer experience while still delivering zero logging, operator lockout, and mathematically enforceable protections that matter for GDPR, HIPAA, and other regulatory regimes. More than a technical walkthrough, this episode is about data sovereignty, compliance by design, and what happens when privacy becomes something enforced by architecture instead of promised by policy.

Gain digital sovereignty now and save costs

Let’s have a look at your digital challenges together. What tools are you currently using? Are your processes optimal? How is the state of backups and security updates?

Digital Souvereignty is easily achived with Open Source software (which usually cost way less, too). Our division Safeserver offers hosting, operation and maintenance for countless Free and Open Source tools.

Try it now!

Download transcript (.srt)
0:00

Imagine treating your company's customer data not like a valuable asset, but like

0:05

weapons-grade plutonium

0:07

Oh, wow, that is a heavy comparison, right?

0:10

But think about it highly toxic

0:13

Incredibly dangerous and I mean virtually impossible to clean up once it leaks

0:18

Yeah, you really can't just put the genie back in the bottle exactly and today

0:22

We are exploring why sending your proprietary data to standard

0:26

You know off-the-shelf AI tools is basically the equivalent of carrying that plutonium

0:31

in a leaky cardboard box

0:33

Which is terrifying for any business totally, but before we unpack the solution to

0:37

this massive vulnerability

0:38

Let's introduce the supporter making today's deep dive possible safe server, right?

0:43

Because if you are running a business an association or really any kind of

0:46

organization, you know

0:47

The struggle relying on proprietary AI tools and cloud services from massive

0:52

vendors like Microsoft or Google

0:53

It often means locking yourself into an expensive black box

0:57

Oh, yeah

0:57

And beyond the unpredictable costs just handing over your sensitive data to these

1:01

tech giants raises some incredibly serious

1:04

legal regulatory and

1:07

Compliance concerns. Yeah data sovereignty becomes critical here

1:11

I mean when we talk about email retention financial records audit trails and strict

1:15

data protection under the law

1:17

Relying on those massive proprietary platforms means losing control

1:21

You don't know where your data lives or who might be looking at it, right?

1:25

Keeping your data on your own terms is a strict legal requirement in a lot of

1:29

industries and that's where safe server comes in

1:31

They help organizations replace those expensive opaque tools with secure open

1:37

source solutions

1:38

And you know often at a fraction of the cost. Yeah, which is a huge win

1:42

Definitely they guide businesses from the initial consulting phase all the way

1:46

through to operation

1:48

Running everything on servers located right in the EU giving you that total control

1:52

exactly

1:53

So if you want to take back control of your infrastructure

1:55

You can find more information at safe server dot DE and that perfectly sets up our

2:00

mission for today. It really is

2:01

We're looking at documentation from the cybersecurity firm confident security along

2:05

with the github repository for an open source framework called open PCC

2:10

So our goal here is to figure out how you can easily jump into using powerful AI

2:15

models

2:16

Without handing over all your confidential data. Yes, and even if you are a total

2:20

beginner to cloud architecture

2:22

Just stick with us by the end of this deep dive. You will understand exactly how to

2:27

secure your AI workflows

2:29

Let's start with the sheer scale of the liability we are dealing with

2:32

We have to completely rethink what data actually is right because people always say

2:37

data is the new oil exactly

2:38

They view it as fuel but the author and activist Cory Doctorow

2:42

He's the one who provides that striking weapons-grade plutonium quote found in our

2:48

sources such a great analogy

2:49

It really is he argues that personal data is dangerous. It's long-lasting and once

2:54

it has leaked

2:55

There is absolutely no getting it back

2:57

Yeah, you cannot unleak a database of confidential customer information or you know

3:02

proprietary source code that a developer

3:03

Accidentally pasted into a public AI chatbot. Oh, man

3:07

We've all read those horror stories somebody just trying to debug a script and

3:10

suddenly the company's IP is in the training data

3:12

Exactly and cryptography professor Matthew D green makes a pretty blunt observation

3:18

about this in our source material

3:20

What does he say?

3:21

He basically notes that in practice if you aren't running an AI model locally on

3:26

your own personal device

3:27

Your alternative is to ship private data to open AI or someplace sketchier

3:33

Where who knows what might happen to some place sketchier? Yeah, that's reassuring

3:37

right security technologist Bruce

3:39

Schneier refers to this exact vulnerability as the pollution problem of the

3:44

information age the pollution problem

3:46

Yeah, we are producing toxic runoff every time we interact with these cloud models

3:51

Just dumping it into the digital ecosystem and hoping it doesn't poison the well

3:55

Wow

3:55

He argues that protecting privacy is the environmental challenge of our time and

4:00

right now the infrastructure

4:01

Most companies use is just fundamentally flawed. Okay, but hold on. Let's look at

4:06

this practically for a second

4:07

A traditional enterprise server has firewalls end-to-end encryption strict identity

4:11

and access management roles

4:13

If shipping data to the public cloud is so sketchy

4:16

Shouldn't a business just self host their own AI models on their own private

4:20

servers? That's the logical next question, right?

4:23

Like how could a bad actor possibly dump the memory if the IT department has done

4:27

their job?

4:29

Configuring those firewalls and access controls. Well the source material from

4:32

confidence security

4:33

Explicitly addresses this assumption

4:36

Traditional self-hosting solutions are actually insufficient for strict compliance

4:41

Wait, really why because they still rely on human trust

4:45

Those firewalls and access management roles you just mentioned they are

4:49

administered by humans

4:51

Oh in a traditional self hosted setup the root system administrator always has

4:55

ultimate access if a bad actor

4:58

Compromises those admin credentials or you know if the server hardware is

5:01

physically accessed they can dump the memory straight from the RAM

5:04

They can read the logs

5:06

So it's a single point of failure the human element exactly from a legally binding

5:11

compliance standpoint

5:13

Trusting the IT department is not a measurable security metric. I mean that makes

5:17

sense. You can't audit a promise, right?

5:19

Traditional self-hosting relies on policies. It's essentially a sticky note on the

5:24

server saying please don't look at this data

5:26

Yeah, that's not gonna hold up in court. No, if an auditor comes knocking you

5:30

cannot mathematically prove that the data remained unseen

5:33

We have to remove human trust from the equation entirely and build a system that

5:38

relies on math instead of policies

5:40

Which brings us to the open source blueprint that's attempting to solve this

5:43

problem

5:44

Open PCC. Yes. It's a framework designed specifically for provably private AI

5:49

inference

5:50

It's written mostly in the go programming language and the github repository

5:54

already boasts

5:56

928 stars, which is pretty impressive traction

5:59

Definitely and the architecture was heavily inspired by Apple's private cloud

6:03

compute

6:04

Which millions already rely on for secure AI features?

6:07

But open PCC takes those core principles and makes them fully open auditable and

6:12

deployable on your own infrastructure

6:14

And people in the industry are definitely taking notice a user named abalone on

6:18

hacker news called this server engineering

6:21

Insanely next level insanely next level. Yeah, they compared the magnitude of this

6:26

shift to the massive industry transition to

6:29

Stateless architecture 30 years ago or the move to microservices 15 years ago. Wow,

6:34

those were massive paradigm shifts

6:36

Let's break down why abalone makes that comparison

6:38

Because microservices completely changed how applications were built right by

6:43

breaking massive

6:45

Monolithic applications into small independent pieces, right? So if a one piece

6:49

failed the whole system didn't just crash

6:52

Right and open PCC is attempting a similar foundational shift, but for privacy it

6:57

breaks the assumption of trust

6:59

Exactly instead of trusting a single monolithic server and its administrator with

7:03

all your data

7:04

Open PCC distributes and cryptographically secures the process

7:08

So no single entity holds the keys not even the machine's owner

7:12

It enforces this through encrypted streaming unlinkable requests and something

7:16

called hardware attestation. Okay, let's pause right there

7:19

hardware attestation

7:21

That is a very dense technical concept is yeah for the listener who doesn't have a

7:26

background in cryptography

7:27

Let's do an explain like I'm five breakdown

7:30

How does hardware actually attest to something and why does that replace the need

7:35

to trust the IT guy?

7:37

Okay, think of hardware attestation like a digitally enforced wax seal on an

7:42

envelope

7:43

But built directly into the physical microchip of the server a wax seal on the

7:47

microchip

7:48

Okay

7:48

so when a server boots up a

7:50

Specialized security chip on the motherboard takes a mathematical snapshot of the

7:54

exact code running on the machine

7:56

It measures the operating system the applications everything like taking a

8:00

fingerprint of the software exactly

8:01

And if an administrator tries to secretly install malicious software to spy on your

8:07

data that mathematical snapshot changes

8:09

The fingerprint is different. Oh, I see

8:11

So before your phone or your computer sends any sensitive AI prompts to that server

8:16

It asks the server for that specific mathematical proof if the proof doesn't match

8:21

the publicly audited

8:22

Safe region of the code your device simply refuses to send the data Wow

8:28

So you are no longer trusting an administrator's promise. Nope. You are verifying a

8:31

cryptographic guarantee generated by the physical silicon itself

8:35

That is brilliant

8:38

Okay, so we've covered how we trust the code running on the machine

8:42

But there is another major mechanism mentioned in the github repo called an oblivious

8:48

HTTP relay or OH TTP

8:50

Yes, this seems to handle how the data actually travels to the server. Let's try an

8:54

analogy to visualize this. It's like

8:57

Sending a highly confidential letter to a brilliant consulting detective. Okay, I

9:01

like where this is going

9:02

But instead of taking it yourself you give the letter to a blindfolded courier

9:05

The courier knows where the detective's office is but has absolutely no idea what

9:09

is written inside the letter because it's locked in a safe

9:11

The detective receives the safe

9:13

Opens it using a special key reads the problem and writes a solution

9:18

But the detective has no idea who the courier works for or who originally sent the

9:23

letter that analogy perfectly

9:25

Isolates the mechanics of the OH TTP relay you are completely separating who is

9:30

asking the question from what they're asking

9:32

The who from the what exactly the relay acts as the blindfolded courier when you

9:37

send an AI prompt

9:39

Your IP address your identity goes to the relay but the pump itself is encrypted,

9:43

right?

9:44

The relay forwards the encrypted prompt to the server actually running the AI model

9:48

that compute server decrypts

9:49

The prompt generates the answer and sends it back

9:52

So the compute server knows what the prompt was but it only sees the IP address of

9:56

the relay not you

9:58

Yes, and the relay knows who you are, but only sees encrypted gibberish

10:02

Neither party holds the full puzzle making it impossible to link your identity to

10:06

your proprietary data

10:08

Okay, having an open-source framework with hardware attestation and blindfolded

10:12

couriers is incredible for deep tech engineers who want to build custom

10:16

infrastructure

10:16

Oh, absolutely, but for a beginner developer or midsize business

10:20

I mean building that from scratch requires a PhD in

10:24

Cryptography we need an easy entry point which brings us the practical application

10:29

of this framework

10:30

Our sources introduce a managed service called cone FSC operated by a firm named

10:35

confident security

10:36

All right. This service is built entirely on the open source open PCC standard

10:41

operating under a core philosophy of four words

10:44

Don't trust verify don't trust verify. I love that

10:48

Yeah, and they detail specific technical guarantees to back up that philosophy

10:52

because they utilize the open PCC framework

10:55

They offer zero logging wait zero logging at all zero

10:59

And that doesn't mean they promise to delete your logs at the end of the day

11:02

It means the system architecture literally prevents data from being logged in the

11:06

first place. This is a huge distinction

11:08

It is your prompts are never used for AI training and they are never sent to third

11:12

parties and most crucially

11:13

Even the operator of the server does not have privilege access to the private

11:17

computation

11:18

Okay, let's dig into that operator lockout because this directly addresses our

11:22

earlier discussion about the flaws of self-hosting

11:24

Yeah, if confident security physically owns the server in their data center

11:29

How are they physically locked out of reading the data processing on their own

11:34

machine?

11:35

It comes down to secure enclaves within the processor itself

11:39

When your encrypted prompt reaches the server

11:43

It isn't decrypted in the standard open memory of the computer where an

11:46

administrator could see it

11:48

Where does it go?

11:49

It is routed into a heavily isolated section of the CPU called an enclave

11:54

You can think of it as an impenetrable black box built into the silicon

11:58

So the data is decrypted inside that black box

12:00

Yes

12:01

The AI model generates the response inside that black box and the response is

12:05

encrypted before it ever leaves

12:07

Incredible. So if the server operator dumps the machine's RAM or even attaches a

12:11

physical pro to the motherboard to spy on the data in

12:14

Transit like physically hacking the machine exactly all they will capture is

12:18

encrypted noise

12:18

The administrator of the operating system is entirely blind to what is happening

12:23

inside the enclave

12:24

You know from a development standpoint not having to rewrite an entire application

12:27

Just to integrate a new security standard saves months of engineering time. Oh

12:33

without a doubt

12:33

This was a striking detail in the confidence security documentation

12:37

they provide an open AI compatible API and SDK a

12:42

Developer doesn't have to learn a completely new protocol to use this providing a

12:46

standard interface to leading large language models

12:49

Drastically lowers the barrier to entry you simply swap your existing endpoint URL

12:55

and your API key to visualize that API swap

12:58

It's like having a freight train carrying sensitive cargo

13:01

You don't need to rebuild the train the tracks or the cargo from scratch to make it

13:04

secure, right?

13:05

You just flip a digital switch on the tracks routing the exact same train into a

13:09

highly secure verified vault

13:10

Instead of an open warehouse. That's a great way to put it

13:13

The infrastructure does the heavy lifting while your application continues

13:17

functioning exactly as it did before and beyond accessing leading LL M's

13:21

The documentation notes that users can host manage and sell their own custom models

13:25

with those exact same verifiable privacy guarantees

13:28

Yes, and this brings us to the cost factor

13:32

proprietary black box AI from major vendors is notorious for unpredictable billing

13:37

structures

13:37

Oh, tell me about it. The bills can just skyrocket overnight, right?

13:41

Confident security tackles that by offering transparent pricing where you pay only

13:45

for what you use

13:46

With base fees pinned to current market prices per model

13:50

So organizations aren't forced to pay a massive premium just to secure their data

13:54

Exactly, they get the state-of-the-art security standard without price gouging. Let's

13:59

transition to the ultimate application of all this

14:02

We've mapped out the architecture the secure enclaves and the easy API swap

14:07

But for modern businesses the biggest hurdle to adopting AI is navigating the

14:11

massive legal headaches around data compliance

14:14

Oh, absolutely. Those legal hurdles are defined by strict regulations like GDPR in

14:18

Europe CCPA in California

14:20

HIPAA and the healthcare sector and the fines for messing those up are no joke

14:24

severe penalties for mishandling personal data

14:27

But by utilizing verifiable privacy where an organization can mathematically prove

14:31

that data is encrypted unseen and unlogged

14:34

Businesses can finally leverage powerful AI models on private data while remaining

14:40

strictly compliant

14:41

Let's put this into a real-world scenario

14:44

Imagine an auditor walks into a hospital's IT room to verify hyper a compliance

14:49

regarding a new AI diagnostic tool

14:52

Okay stressful day for the IT guy right in a traditional setup that involves weeks

14:57

of pulling server logs

14:59

interviewing IT staff about access controls reviewing I am policies and ultimately

15:04

just

15:04

Hoping no internal staff member accidentally left the database exposed. It's a

15:08

total nightmare

15:09

But with verifiable privacy through a framework like open PCC

15:14

What actually happens during that audit the audit transforms from a procedural

15:18

nightmare into a mathematical certainty?

15:20

The auditor doesn't need to interview the IT staff or comb through thousands of

15:24

lines of access logs. Really just skip all that

15:26

Yeah

15:27

They simply verify the cryptographic signature of the hardware attestation in a

15:30

matter of seconds

15:32

They can run a mathematical proof confirming that the server is running the audited

15:35

code and that the secure enclaves are active

15:38

the proof demonstrates that no human not even the system administrator could

15:42

possibly have read the patient data as

15:44

The documentation concisely puts it this technology provides peace of mind for the

15:49

business and a piece of cake for the auditors

15:51

A piece of cake for the auditors

15:53

I bet they'd love that a study referenced in the sources by Mazuma Hassan, Andrei

15:58

Kushnaruk and Elizabeth Boricki

16:00

Emphasizes this exact point. Oh, yes

16:03

They noted that integrating privacy by design technologies into AI applications

16:07

Could mitigate the massive challenges of adopting AI and healthcare and healthcare

16:12

is the ultimate stress test

16:14

He really is patient records are the most sensitive plutonium

16:17

There is if we can solve AI privacy for healthcare using these zero-knowledge

16:22

environments

16:23

We can solve it for banking legal human resources everything and the sources frame

16:28

this level of privacy

16:29

Not as a luxury add-on but as an essential baseline for the future of the Internet

16:33

I mean it should be Gary Kovacs states in the materials that security and privacy

16:37

guarantees are strongest when they're entirely technically

16:41

Forcible it shouldn't rely on a company's goodwill or a complex legal contract,

16:47

right?

16:47

Because goodwill changes when profits drop exactly it must be baked directly into

16:51

the code and the silicon and

16:52

Venture capitalist Fred Wilson predicts that the company's doing the best job

16:56

managing user privacy will ultimately become the most successful

17:00

Turning privacy into a core competitive advantage

17:04

Marco Altea at toast ring AI captures the underlying philosophy perfectly

17:10

He argues that privacy is not an option and that it shouldn't be the price we

17:14

accept for just getting on the internet

17:15

That's a powerful statement. It is we shouldn't have to surrender our right to

17:19

digital privacy or expose our company's intellectual property

17:22

Just to participate in the modern AI driven economy tools like open PCC provide the

17:28

technical means to finally refuse that trade-off

17:30

We are witnessing a necessary transition from an era of security by policy to an

17:35

era of security by mathematics and architecture

17:38

Beautifully said let's briefly recap the journey we've taken today. We started with

17:43

the reality of data as weapons grade plutonium

17:46

toxic permanent and

17:49

Constantly being leaked into opaque proprietary cloud models, right?

17:53

We broke down why traditional self-hosting and firewalls fall short because they

17:57

still rely on vulnerable human administrators

18:00

We human elements exactly then we explored the open PCC framework discovering how

18:05

hardware attestation acts as a digital wax seal

18:08

And how oblivious HTTP relays function as blindfolded couriers to separate identity

18:14

from data

18:15

Which is such a massive leap forward it is and we saw how accessible this has

18:19

become through managed services like confident securities

18:22

Kind of SCC where securing an application is as simple as flipping a switch on the

18:26

API tracks

18:27

Utilizing secure CPU enclaves to guarantee operator lockout

18:31

It provides the master key for compliance

18:33

Allowing organizations to navigate strict regulations like GDPR and hyper through

18:37

mathematically enforceable proofs all without sacrificing the efficiency of

18:41

artificial intelligence

18:42

Or paying exorbitant premiums, which brings us perfectly back to the supporter of

18:46

today's deep dive safe server

18:49

If the capabilities we just outlined true data sovereignty

18:53

mathematically enforceable compliance

18:56

Predictable cost structures and protection from massive cloud vendor lock-in if

19:00

that aligns with your organization's needs

19:03

Safe server is the solution. Yeah, absolutely

19:05

Whether you are a business an association or any group looking to replace expensive

19:10

opaque AI tools

19:11

They provide the necessary expertise safe server is really a partner in your

19:16

infrastructure

19:17

They can be commissioned for specialized consulting to help find and implement the

19:21

exact open source solution for your specific needs, right?

19:24

So whether the perfect fit is the open PCC software we explore today or a

19:28

comparable open source alternative

19:30

They guide you from the planning phase all the way through to secure operation on

19:34

servers located right in the EU

19:36

You can learn more and take back control of your data at safe server de

19:39

Before we wrap up though. There is a final thought. I want to leave you with to mull

19:44

over. Okay, let's hear it

19:45

We began by discussing the pollution problem of the information age, you know

19:49

The toxic runoff of data we leave behind when using standard AI platforms

19:54

Right if mathematically enforceable zero-knowledge AI architectures become the new

19:58

default

20:00

What happens to the massive tech empires build entirely on harvesting and monetizing

20:05

our data plutonium?

20:06

Oh, that is a fascinating question

20:08

If we stop providing the toxic runoff could the information age finally clean up

20:12

his pollution problem and force those empires to find a completely

20:15

and we'll see you the next deep dive

20:15

and we'll see you the next deep dive