Architecture choices

Choose where your
data belongs.

Cloud, blockchain and the Safe Network solve different problems. Start with what users need to own, share and recover. Then decide which parts of your product need each kind of infrastructure.

Explore architecture assessment

Compare the roles

Three different jobs.

Cloud services

A provider runs the infrastructure while your product manages its own data and access rules.

When to consider it: Useful when existing services, predictable operations and familiar integration patterns are central to the product.
Question to test: Which data must stay under your organisation's control, and which parts can users own?

Public blockchains

A shared ledger lets independent parties verify a common record of events.

When to consider it: Worth considering when several parties need a verifiable shared state without one operator deciding the record.
Question to test: Does this action need public agreement, or would a private data flow serve users better?

The Safe Network

A distributed network designed for private apps and user-owned data.

When to consider it: Explore it when ownership, private storage and access by design are core product requirements.
Question to test: How will access, recovery, performance and your existing services work together?

Take a focused first step

Test one real user journey.

Trace who reads and writes the data, what happens when access is lost and how the product works with its current services. A small test makes the trade-offs visible before a wider migration.

Understand the Safe Network Plan a scoped migration Discuss Your Project