Bomy brings search, reasoning and accumulated knowledge into one continuous intelligence.
One intelligence.
Every device you allow.
Bomy brings AI, verified knowledge, secure messaging, user-owned vaults and permissioned action into one personal intelligence ecosystem.
Android · iPhone beta in preparation — coming soon
Some parts are available today; others are actively in development.

More than a chatbot. One Bomy ecosystem.
Bomy is not only AI that answers. It connects intelligence, verified knowledge, secure messaging, user-owned storage and permissioned action — each with clear boundaries.
Useful knowledge shouldn't disappear after one conversation. Bomy is designed to keep approved knowledge with context, provenance and boundaries so it can be found, checked and reused.
Bomy's secure, resilient messenger direction — built for conversation continuity across devices and changing connectivity.
User-owned storage for your source data, kept separate from the AI Knowledge Library — access is not ownership.
Bomy Agent is being built to turn intent into controlled action: plan first, ask when permission is needed, execute within a defined scope, then verify the result.
From personal devices to servers and, over time, specialized systems, Bomy is designed to bring the same intelligence closer to where work happens — without turning access into ownership.
How Bomy protects your data
Access, AI use, external-model transfer, sharing, training and publication are not one blanket permission.
See how Bomy protects your data- Private by defaultUploading is not publishing.
- Purpose before useAccess does not authorize every purpose.
- Search only what's allowedAuthorized scope is resolved before AI retrieval.
- Honest encryptionWe distinguish who can decrypt.
One intelligence. Many authorized endpoints.
Bomy is not designed to take over a device. It is designed to work through the permissions, tools and boundaries you give it — each endpoint appears only as an authorized connection.
- Mac
- Windows
- Linux
- iPhone
- Android
- Server
- Robot
- Industrial Systems
It searches and verifies before it answers.
Bomy is designed not to treat the first retrieved result as truth. It is built to look for evidence, compare sources, and present answers in a structured way.
- Search and compareDesigned to find and compare multiple sources and check for contradictions
- Structured answersOrganizes key points into lists and steps; copy or regenerate
- Choose response speedPick a response mode such as “Fast” to fit the moment
Action should have a protocol.
- 01Intent
Understand what you want.
- 02Plan
Turn the goal into explicit steps.
- 03Permission
Ask before crossing a meaningful boundary.
- 04Action
Execute only within the approved scope.
- 05Verify
Check the outcome and keep an accountable result.
Plan before action. Permission before execution. Verification after every action.
Information can guide an action. It cannot authorize one.
Good knowledge shouldn't vanish after a single answer.
Bomy is being built to preserve source provenance, versions, and evidence relationships so knowledge can be searched and checked again. The Knowledge Library is distinct from your Personal Vault.
Your source data remains your data. Bomy's derived knowledge is a separate layer.
- Source v1
- Candidate
- Verify · provenance · policy · time
- Approved knowledge v1
- New evidence
- Candidate v2
- Supersede · contest · approve → v2
Knowledge can change without losing its history.
Every answer can trace back to a source, a version and the moment it was approved.
Intelligence should not mean unlimited authority.
Least permission
Bomy is designed to receive only the access needed for the current task.
Local veto
A device can refuse an action even when a remote plan exists.
Independent safety
For safety-critical systems, AI must never replace independent safety controls.
Access is not ownership.
Keep your media safe,
in a Vault that's yours.
A private, user-owned space for organizing videos, photos, and documents. Your Vault and Bomy's AI knowledge are intentionally separated — a file does not become AI knowledge merely because it lives in your Vault.
- Vault separated from AI knowledgeA boundary so personal files aren't absorbed into AI knowledge automatically
- Sort video, photo, documentOrganized by type so you can find things fast
- Opt-in backupOff by default. Nothing is scanned or uploaded until you turn it on

From private vault to authorized use
- User vault source — private
- Explicit purpose · authorization · minimization
- Encrypted / approved object or reference
- Authorized knowledge or processing
Content addressing does not change ownership. A CID is not consent.
Build with Bomy.
Bring Bomy intelligence into software, terminal workflows, and devices you explicitly authorize.
Developer Platform — In Development
Bomy API
Integrate Bomy intelligence into your software with scoped access, visible usage and controlled budgets.
Bomy CLI
Use Bomy from the terminal through your Bomy account — without pasting a permanent API secret into your shell.
Bomy Agent In Development
Connect Bomy to authorized devices through planning, policy, approval and verification.
An API key authorizes software integrations. It is not device, shell, or agent authority.
Messages should survive the network changing.
Most messaging assumes the network is simply there. MoLink is being built around a harder question: what should happen to a conversation when connectivity becomes slow, intermittent or temporarily unavailable?
- 01Message created
- 02Encrypt · bind to conversation
- 03Send when a path exists
- 04Pending safely when it doesn't
- 05Retry · relay · resume
- 06Delivered · history continues
Secure by message lifecycle
Encryption, device state and delivery state are treated together, not as a static padlock.
Multi-device continuity
Designed so the conversation is the product — not a single device session.
Resilient delivery
Designed to tolerate delay, retry and changing paths rather than treating every interruption as loss.
Disaster / degraded-network direction
Researching local and delay-tolerant paths for cases where ordinary infrastructure is weak or unavailable.
Content-addressed message objects can help verify that what you received is what was referenced — identity and integrity, not a privacy guarantee by itself.
If no physical path exists, delivery waits. The goal is to preserve continuity and resume safely when an allowed path returns — not to pretend physics doesn't apply.
How a MoLink message travels
- Sender
- Encrypt
- Content-addressed message object
- Allowed storage / provider path
- Retrieve · CID verify
- Decrypt
- Authenticated conversation reconcile
The node that returns the bytes is not automatically the sender or the conversation authority.
Address the content, not just the location.
Bomy uses content-addressed objects so an exact object can be referenced and checked independently of the server that returned it. Bomy then adds encryption, authorization, provenance, version lineage and availability controls above that foundation.
server.example/file/123
“Give me whatever is at this location.”
CID bafy…q7k
“Give me the object matching this content identity.”
A CID can identify content. It does not grant permission, prove truth, or provide privacy by itself.
Verification is not one check.
Content identity
What exact object is this?
Authorization & purpose
Who may use it, and for what?
Availability
Can it be retrieved now, from an allowed source?
Knowledge state
Is it current, superseded, contested or approved?
No single layer substitutes for another.
Content identity is not availability.
- Your device
- Encrypted local node
- Redundant provider
- Enterprise replica
- Offline archive
Bomy separates “Is this the exact object?” from “Can I retrieve it right now?” One source can fail while another returns the same verified object.
Not every object carries every replica.
Your data. Your boundary.
Bomy is designed so that access, AI use, sharing, training, publication and external processing are separate decisions — not one blanket permission. Privacy isn't a side effect of using Bomy; the boundary is part of the product.
Private by default
Uploading is not publishing. Private stays private until an explicit publication action changes it.
Purpose before use
Access to data does not automatically authorize every purpose.
Local when appropriate
Designed to keep processing close to the device when policy and capability allow.
Search only what is allowed
Designed to resolve the permitted source set before AI retrieval — not filter private data out after the answer.
Honest key ownership
We distinguish who can decrypt, not just whether data is 'encrypted.'
No silent downgrade
A feature should not quietly weaken your protection level.
Privacy filtering happens before retrieval.
Denied sources never enter the retrieval pipeline.
- Cloud sync
- Local AI
- External AI
- Share
- Training
- Export
- Public publish
Syncing a file does not automatically authorize sharing, training, publishing or sending its raw content to an external model.
We describe who can decrypt — not just whether something is “encrypted.”
A CID identifies content. It does not grant access or consent.
Content addressing is not encryption. Confidentiality comes from encryption and policy, not from a CID.
Signed in does not mean unrestricted. Access is designed to be resource-scoped and least-privilege.
When deletion is requested, Bomy's architecture is designed to revoke active access and process retention or erasure by the object's policy — an offline device isn't claimed wiped until it has acknowledged the command.
- Content addressing → identifies content
- Encryption → protects readability
- Authorization → controls access
- Purpose policy → controls allowed use
- Retention & revocation → controls lifecycle
Start with Bomy.
We show a platform only when it is real. No store badge or download appears until an actual release exists.
- Bomy AI — iPhoneIn DevelopmentLearn more
- Bomy AI — AndroidIn DevelopmentLearn more
- Bomy Desktop — macOS · Windows · LinuxPlatform DirectionLearn more
- Bomy CLI — macOS · Linux · WindowsIn DevelopmentLearn more
- Bomy Agent — authorized devicesIn DevelopmentLearn more
Questions, answered honestly.
What is Bomy?
Is Bomy a web chatbot?
Where can I use Bomy?
What is MoLink?
How does Bomy protect personal data?
What does content-addressing / IPFS do in Bomy?
Does a CID mean data is private or true?
What is Bomy Agent?
Can Bomy act on a device without my permission?
What is Bomy API?
Do I paste an API key into Bomy CLI?
Is Developer API pricing available?
Which products are available vs in development?
What's new.
Public website launched in seven languages, with Arabic right-to-left support.
Privacy-by-boundary and the content-addressed technology foundation published.
Bomy for Developers direction (API · CLI · Agent) introduced — in development.
We add an update only when a real, public-safe milestone exists.
Intelligence you own, close to the devices you use.
Bomy exists to keep control with the person: knowledge that carries its provenance, communication that stays resilient, intelligence that runs close to your devices, and action that happens only with explicit permission and verification.
- You hold the boundary.
- Knowledge keeps its history.
- Communication stays resilient.
- Action is permissioned and verified.
Grounded intelligence, on your device.
We'll let you know the moment Bomy is ready.