Sharp#Soft
Why Sharp#Soft exists

Own your information.
Actually.

Your photos, your messages, the things you write and make — digital, but yours. That should be obvious. On today's internet, it isn't: whoever holds the keys owns the information, and it isn't you. Sharp#Soft is built to change that — provably, not as a promise.

See what owning it means How the machinery works

Two interactive demonstrations below — no scripts, no trackers, just the model.

You don't own what someone else can open

Everything you keep on a mainstream platform lives on their machines, under their keys.

Think about what "your" means for the information you keep online today. The account is a row in the platform's database. The content sits on the platform's servers, stored in a form the platform can read. Your access to your own words is a permission — granted by the operator, revocable by the operator. That is not ownership. That is tenancy.

Because the operator holds the technical capability to open your information, everything else follows from their conduct, not from you:

  • They can read it — and read it for purposes you never see: indexing, profiling, advertising
  • They can lose it — a breach of their systems exposes your information
  • They can lock you out — a suspended account takes your archive with it
  • They can be compelled — what an operator can open, an operator can be ordered to open
  • They can change the deal — terms, prices, and features move under your data, not with it

The things you create

The same holds for what you make. A document you wrote, a design you drew, a plan you drafted — once uploaded, it feels like yours but behaves like theirs. You cannot prove it is yours, you cannot control who reads it, and if the platform disappears or disagrees with you, it is gone.

None of this requires anyone to act in bad faith. It is simply what the architecture makes possible — and architecture, not policy, decides what can happen to your information.

If you don't hold the keys, you don't own it. Every promise a platform makes about your data sits on top of one fact: they can open it and you can't stop them. Ownership begins where that capability ends.

The principle: ownership you can verify

Owning digital information should mean the same thing as owning anything else — and it can.

  1. Only you decide who can open it. Your information is sealed under keys that are created on your device and stay with you. Access is not a permission someone grants you to your own things — it is a capability only you can extend.
  2. You can prove where it came from. What you create carries your signature. Anyone can verify that it originated from you — and that nobody altered it after you signed it.
  3. You can take it and leave. Your information is downloadable, portable, and survivable. Close your account and you — not the operator — remain the authoritative holder of everything you made.

The first two are the pillars this page demonstrates. The third is built in from day one — the whitepaper describes the full download-and-leave model.

Pillar 1 — Own by protection At launch

Sealed to you, and to exactly the people you choose. Nobody else — including us.

The seal is the ownership

In Sharp#Soft, a document or file you share isn't guarded by an access list on a server. It is sealed under a cryptographic lock — Sharp#Soft's SharpCryptLock — and the only way to open it is to be a member of that lock. You, as the owner, decide who the members are.

There is no master key. Not for a support team, not for an administrator, not for Sharp#Soft itself. Our servers store your sealed content as opaque ciphertext — we could not open it even if we were asked to, ordered to, or breached. That is what makes it yours: the ability to open it exists only where you put it.

Removing someone is just as real. When you remove a member, the lock is cryptographically re-keyed — future content, and content they never got around to opening, is structurally out of their reach. Not "access revoked" in a database: the door itself is changed.

The honest boundary: no system can recall what an invited member already opened and copied while they were a member. Cryptography controls who can open the door — not what people do with what they carried out. Choose who you invite; the architecture holds everything else.

Try it — who can open a sealed document?

A file, renovation-plan.sharp, sealed under a lock you own. Invite your two collaborators in or out and watch who the seal admits. There is no setting behind this and no permission table — the lock's membership is the access.

Members:
  • You (Owner) Can open
  • Alva Can openmember of the lock Sealednot a member
  • Ben Can openmember of the lock Sealednot a member
  • Sharp#Soft servers Sealedhold only ciphertext
  • A platform administrator Sealedno master key exists
  • Anyone else Sealed

The bottom three rows never change — that's the point. No toggle on any server, no role in any company, can add Sharp#Soft or an outsider to your lock. Only the owner extends membership, and membership changes are cryptographic re-keys, not checkbox flips.

Pillar 2 — Own by provenance At launch

What you create can carry your signature — proof of origin that travels with the information itself.

Yours, verifiably

Owning what you create also means being able to prove it came from you — and that nobody changed it afterwards. In Sharp#Soft, every Identity carries its own signing key, created on your device like every other key. A signed message or document is cryptographically bound to the Identity that signed it and to its exact content at the moment of signing.

Shared spaces can carry a signature of their own: a space can hold its own signing key, and members you trust with the Signer role can sign under it — so a document can prove it came from this team's space, not just from one person.

Verification needs no authority, no support ticket, and no trust in a platform: the signature checks out against the signer's published identity material, or it doesn't. Change one character of the content and the check fails. Tamper-evidence is not a review process — it is arithmetic.

The honest boundary: a signature proves which Identity's key signed the content and that it hasn't changed since. It cannot tell you what was altered, and it cannot judge whether the signer's words are true — provenance is about origin and integrity, not about content.

Try it — verify where information came from

A signed quotation arrives. Check it against the signer's published identity material — then flip the switch to alter one figure in transit, the classic invoice-fraud move, and watch verification react.

Signed by:

From: Maria · Work Identity From: Project Alder · shared space

Quotation for the kitchen renovation: materials and labour, total 45,000 kr95,000 kr, payable on completion. Valid for 30 days.

✓ Verified — signed by Maria's Work Identity, content intact since signing ✓ Verified — signed under Project Alder, content intact since signing ✕ Verification failed — the content is not what was signed, or the signature is not from the claimed origin

The altered figure is a 50,000 kr difference an eye would miss — and a signature check cannot. Anyone holding the signer's public identity material can run this verification; there is no authority to petition and no platform to trust.

Two internets

The same activities — keeping, sharing, creating — under two opposite ownership models.

The platform-owned internet

Your information, their keys

  • Your account is a row in their database; access is a permission they grant
  • Content is stored so the operator can read it — and therefore monetise it
  • "Who made this?" is answered by trusting the platform's records
  • A lockout, breach, or shutdown takes your information with it
  • The business model is you: attention, profiles, advertising

The you-owned internet — Sharp#Soft

Your information, your keys

  • Your Account opens only with the credential you hold — servers store sealed ciphertext
  • Content opens for the identities you chose — no master key, not even for us
  • "Who made this?" is answered by a signature anyone can verify
  • Download everything, any time; close your account and remain the authoritative holder
  • The business model is honest: we sell subscriptions — we don't sell you

This is the point of Sharp#Soft

Privacy by architecture is how we build it. Ownership is why. Everything on this page ships with version 1.0 in 2026.

How it works

The machinery behind these pillars, step by step — sealing on your device, identities without email, CryptLock, a message followed end to end.

The whitepaper

The full argument, including the limits: what is protected, how, where the boundaries lie, and how to verify every claim yourself.

The product tour

What owning your information looks like in the app — secure files, sealed documents, private messaging, calendar, and shared spaces.

Make it yours.

Sharp#Soft launches in 2026, Windows first. Leave your address and we'll tell you the moment it's ready — nothing else, ever.

Get notified at launch Read the whitepaper