Over the last few posts, we have written about a larger question.

What happens when people no longer have a meaningful place where their own data lives?

We explored how the internet changed from something people accessed through personal computers into something increasingly built around remote platforms, cloud accounts, and services that sit outside the user’s control. We also introduced the idea of the Personal Internet: a different direction for personal data, connectivity, and data ownership.

But ideas are not enough on their own. At some point, the question has to become more practical.

Where does personal data actually live? How does a person access it? What does the experience look like? How does it connect across devices? How does it work at home, remotely, and in real environments that are not perfectly controlled?

That is where Project Canopy begins.

From Concept to Infrastructure

Project Canopy is DFLab’s infrastructure project for turning the idea of a Personal Internet into something practical.

It is not only a research direction. It is not only a design concept. It is not just a statement about data ownership. It is a system we are building, testing, and refining.

The purpose of Project Canopy is to explore what it takes for people to have their own digital base. A place where personal data can live closer to the person who owns it, instead of beginning by default inside someone else’s platform.

This does not mean rejecting the internet. It does not mean disconnecting from modern services. It does not mean trying to recreate everything from scratch.

It means changing the starting point.

Instead of assuming that personal data should begin in the cloud and be accessed by personal devices, Project Canopy starts from the opposite direction:

personal data should have a user-controlled base, and the broader internet should connect around that base where needed.

Why It Starts with a Device

One of the earliest decisions behind Project Canopy was that personal ownership needs somewhere to exist.

Data ownership cannot only be a setting inside an account. It cannot only be a sentence in a privacy policy. It cannot only be a permission toggle that can be changed later by a platform.

For ownership to become practical, there needs to be infrastructure that belongs closer to the user. That is why Project Canopy begins with a small personal device.

The device is the first physical layer of the project. It gives the idea of personal infrastructure a place to begin. Rather than treating personal data as something that must immediately live inside a remote platform, Project Canopy starts with the idea that a user should have their own base.

At this stage, the focus is not on making that device do everything at once. The focus is on the foundation.

Can it be set up clearly? Can it be accessed reliably? Can it become understandable to someone who is not deeply technical? Can it become a practical part of someone’s online environment instead of another complicated piece of technology?

Those questions matter because infrastructure is only useful if people can actually use it.

What We Are Testing Now

Project Canopy is currently being tested through closed development and beta stages.

The focus of this stage is not to present a finished product. The focus is to learn how the system behaves with real users, real devices, and real home networks.

We are testing the foundations: setup, access, reliability, usability, and the overall experience of interacting with personal infrastructure.

That may sound simple, but it is one of the most important parts of the project. A system like Project Canopy cannot only work in theory. It has to work in ordinary environments, with ordinary expectations, and with enough clarity that people understand what they are using.

We are not only asking whether individual features work. We are asking whether the system makes sense as a whole.

Can someone understand what the device is for? Can they begin using it without needing to understand every technical layer beneath it? Can the experience communicate enough without overwhelming the user? Can the system become something that feels approachable rather than experimental?

These are the questions that shape the current stage of Project Canopy.

Why We Are Revealing It Gradually

We are introducing Project Canopy carefully because the work is still evolving.

There are parts of the system already being tested. There are parts still being refined. There are also parts of the long-term direction that should not be rushed into public language before the foundation is ready.

This is why we have spent time first explaining the thinking behind the project. The Personal Internet is the direction. Project Canopy is the system we are building toward that direction.

From here, we can begin to talk less abstractly and more practically about the layers involved, without trying to reveal everything at once.

The important shift is this: Project Canopy is not just about imagining a better relationship between people and their data. It is about building the infrastructure that relationship would require.

The First Layer

Every large change begins with a first layer.

For Project Canopy, that first layer is not a fully formed ecosystem. It is not a complete replacement for every service people use today. It is not a promise that everything will immediately move away from the systems people already rely on.

The first layer is simpler and more important. A user-controlled base. A physical starting point.
A foundation for personal data and access. A system that can grow over time. That is what we are building now.

Project Canopy is the first practical step in DFLab’s work toward the Personal Internet.

Not just as an idea. As infrastructure.