Most businesses that ask us about blockchain do not need one. The ones that do usually need to answer one question first: who has to trust the record, and who is allowed to write to it. That answer decides whether a private network is enough or a public chain is worth the cost.
What a blockchain actually gives you
Strip away the marketing and a blockchain is a shared ledger with three properties. Every entry is signed by whoever added it. Entries are appended in order and cannot be changed without everyone noticing. And more than one party holds a full copy, so no single party can quietly rewrite history.
If you only need the first two, a well-designed database with an audit log does the job for less. The third property is the one that matters. It is only valuable when the parties who share the record do not fully trust each other, or when outsiders need to check the record without asking you for permission.
Private networks
A private network, often called a permissioned network, is one where you decide who runs the nodes and who can read or write. The usual setup is a small group of known organisations: a company and its suppliers, a group of lenders, a few agencies that share a register.
A private network is usually enough when:
- Every participant is known, has signed an agreement, and can be held to it.
- The data is confidential and must not be visible to the public.
- You need predictable throughput and no transaction fees paid to third parties.
- Regulation requires you to know where the data lives and who holds it.
The honest limit is that a private network is only as trustworthy as its members. If one company runs most of the nodes, the others are trusting that company, and you have built an expensive database. A private network earns its keep when the nodes are spread across parties with different interests, and when the governance (who can join, who can be removed, how rules change) is written down before the first block.
Public chains
A public chain is run by operators you do not control and did not choose. Anyone can read it, and anyone who pays the network's fee can write to it. You give up control and privacy, and in return you get a record that nobody, including you, can alter or switch off.
A public chain is worth it when:
- Customers, partners or regulators need to verify something without trusting your servers. Proof that a document existed at a point in time, or that a credential was issued, fits here.
- Your product issues tokens or assets that people hold in their own wallets and use outside your system.
- You want to plug into existing wallets, exchanges or protocols rather than build that ecosystem yourself.
- The business case depends on the record outliving your company.
The limits are real. Fees vary with network demand and are not in your control. Everything you write is permanent and public, so personal data must stay off chain, with only a hash or reference on it. A mistake in a smart contract cannot be patched after the fact the way a normal deployment can, so testing and review carry more weight. And your users need wallets, which adds friction you must design around.
A middle path
Many real systems use both. The day-to-day work happens in a private network or a plain database, where it is fast and confidential. At intervals, a fingerprint of that record is written to a public chain, so anyone can later prove that the private record was not changed. You get confidentiality and predictable cost for the bulk of the work, and public proof where it counts.
| Question | Private network | Public chain |
|---|---|---|
| Who needs to trust the record | Known partners | Anyone, including strangers |
| Who can see the data | Members only | Everyone |
| Who sets the fees | You and your partners | The network |
| Who can change the rules | Your governance group | Nobody, in practice |
| Who keeps it running | You | Independent operators |
How we approach it
When you bring us a blockchain idea, the first thing we do is check whether you need one. If a database with signed audit entries solves the problem, we say so. If more than one party needs to hold the record, we help you decide which parties, what they can see, and how the rules change, and we design the network around that.
We build private networks, public chain integrations and the hybrid pattern above, from our studio in Kelowna for clients across Canada, in the United States and worldwide. If you want a sense of what a build would cost before we talk, the estimator gives a price range in minutes, with build cost, monthly costs, effort by role, weeks and every assumption listed. Run it once for the private version and once for the public one, and the difference in monthly cost will tell you a lot about which path fits.
