Private communications for organisations that need tighter control
SemaFore is designed for communication that should stay between the intended parties, without relying on consumer messaging habits or weak handling of shared information.
Product
SemaFore
SemaFore is a secure messaging platform for organisations that need their internal communications infrastructure to be genuinely private.
Built for communication that should stay contained
SemaFore is for teams that need secure messaging to be routine, usable, and easier to govern, not an awkward exception reserved for only the most sensitive exchanges.
See the full technical picture
The SemaFore site contains the security architecture, deployment information, and product details in full.
Visit semafore.io
Product details
How SemaFore is structured
The sections below set out the operating model, the cryptography, and the deployment assumptions behind the product.
What SemaFore is
SemaFore is a secure messaging platform for organisations that need their internal communications infrastructure to be genuinely private - administered by the organisation, encrypted on device, and inaccessible to anyone outside it.
It is intended for professional environments where communications sensitivity is a legal or competitive matter: government agencies, public sector bodies, M&A advisory, private equity, legal practice, and executive teams handling information that should not sit on platforms with conflicting commercial interests.
How it is different
Most enterprise messaging sits on infrastructure run by companies with a commercial interest in the data that passes through it. SemaFore does not.
Messages are encrypted on the sender’s device before transmission, using the Signal Protocol - X3DH key agreement and Double Ratchet forward secrecy. SemaFore’s servers store and relay ciphertext only. Encryption keys are generated on each user’s device and are never transmitted to our infrastructure. There is no technical mechanism for us to read message content.
This is an architectural property, not a policy one. It does not depend on promises; it depends on mathematics.
Who administers it
Each deployment is owned by an organisation. A designated administrator - typically an IT manager or a senior operations person - controls who has access, approves new devices, and manages the organisation’s configuration through a web-based administration portal.
Administrators have full visibility of who is in the organisation and full control over access. They cannot read message content. The separation is deliberate: the person responsible for running the platform should not be in a position to compromise its confidentiality.
The audit trail
Administrative actions and authentication events are recorded in an audit log; scope and retention are set out in the SemaFore security information.
Deployment
The core messaging service and ciphertext storage run on Attomus-owned hardware in the United Kingdom. The public website and portal interface run on Cloudflare; the SemaFore privacy notice explains the processing boundaries.
On-premise deployment within your own infrastructure is available under contract. Contact SemaFore for a scoped discussion of requirements, dependencies and delivery.
Getting started
Apply to evaluate SemaFore. After approval, the nominated administrator receives access instructions for the provisioned organisation. Application, approval and access are separate steps.
Larger deployments and enterprise requirements are handled differently. If your organisation has complex data residency, air-gap, or compliance requirements, speak to us directly before onboarding.
The Attomus connection
SemaFore is an Attomus product. It is built on the same principles that govern everything Attomus makes: no advertising, no data monetisation, UK jurisdiction, and products designed so that the provider’s access to your information is minimised by architecture rather than promised by contract.
Further information
The SemaFore website contains the full technical documentation, security architecture, pricing, and deployment information.