Skip to content
RavenFlo
  • Platform Messaging, calls, documents and automation on one encrypted platform.
  • Messaging Chats, groups, files and voice notes your people already understand.
  • Calls and meetings Voice and video that stay inside your network.
  • Documents Versions, permissions and retention on your servers.
  • Integrations Approvals and alerts from the systems you already run.
  • Control Tower Identity, devices, policies and audit in one console.
  • Board Agendas, papers and minutes. Coming 2027.
Featured Read the security whitepaper How encryption, device keys and the compliance archive actually work.
  • Security Encryption, keys and what your servers can see.
  • Trust centre Commitments, supply chain and the status of audits.
  • Responsible disclosure How to report a vulnerability.
  • Whitepaper The security design, written in full.
For security teams Talk to a security engineer Walk the architecture on your own infrastructure, with your directory.
  • Deployment overview Your data centre, your disaster-recovery site, your branches.
  • On-premise Headquarters, disaster recovery, branch edge and a DMZ relay.
  • Private cloud The same software in a cloud account your organisation owns.
  • Sizing guide How RavenFlo is laid out before anyone quotes a server count.
  • Architecture Where the apps, the servers and your directory meet.
With an engineer Book an architecture session A deployment plan for your sites, your directory and your devices.
  • Banking and financial services Treasury, credit, branches and the board, with an audit trail.
  • Government and public sector Official conversations on infrastructure you operate.
  • Healthcare Care coordination without consumer chat.
  • Manufacturing and energy Plant, site and head office, including on weak networks.
  • Conglomerates Many companies, one messenger, group-level control.
On your infrastructure Request a demo See RavenFlo with your directory and a deployment plan.
  • Resource library The whitepaper, architecture, sizing and the blog.
  • Security whitepaper The design a CISO can read and question.
  • Architecture overview Apps, encrypted transport, your servers, your controls.
  • Sizing guide Roles for headquarters, recovery and branches.
  • Blog Practical writing for security, compliance and IT.
Start here Security whitepaper Plain words first. The design detail follows.
  • About Why the messenger is named for a bird that comes home.
  • Careers How we hire, and where to write.
  • Partners For firms who deploy software inside a customer’s walls.
  • Blog Notes from the work.
  • Contact Sales, support, security and press.
  • Request a demo 45 minutes with a solutions engineer.
Next step Request a demo The apps, the encryption, Control Tower and a plan for your sites.
Sign in Request a demoDemo
Product Platform Messaging, calls, documents and automation on one encrypted platform. Messaging Chats, groups, files and voice notes your people already understand. Calls and meetings Voice and video that stay inside your network. Documents Versions, permissions and retention on your servers. Integrations Approvals and alerts from the systems you already run. Control Tower Identity, devices, policies and audit in one console. Board Agendas, papers and minutes. Coming 2027.
Security Security Encryption, keys and what your servers can see. Trust centre Commitments, supply chain and the status of audits. Responsible disclosure How to report a vulnerability. Whitepaper The security design, written in full.
Deployment Deployment overview Your data centre, your disaster-recovery site, your branches. On-premise Headquarters, disaster recovery, branch edge and a DMZ relay. Private cloud The same software in a cloud account your organisation owns. Sizing guide How RavenFlo is laid out before anyone quotes a server count. Architecture Where the apps, the servers and your directory meet.
Solutions Banking and financial services Treasury, credit, branches and the board, with an audit trail. Government and public sector Official conversations on infrastructure you operate. Healthcare Care coordination without consumer chat. Manufacturing and energy Plant, site and head office, including on weak networks. Conglomerates Many companies, one messenger, group-level control.
Resources Resource library The whitepaper, architecture, sizing and the blog. Security whitepaper The design a CISO can read and question. Architecture overview Apps, encrypted transport, your servers, your controls. Sizing guide Roles for headquarters, recovery and branches. Blog Practical writing for security, compliance and IT.
Company About Why the messenger is named for a bird that comes home. Careers How we hire, and where to write. Partners For firms who deploy software inside a customer’s walls. Blog Notes from the work. Contact Sales, support, security and press. Request a demo 45 minutes with a solutions engineer.
Sign inCustomer documentation Request a demo
  1. Home
  2. Accessibility

Legal · Effective 11 November 2026

Accessibility statement.

This website is built so that people can read it, navigate it with a keyboard, and use it with assistive technology. We aim for WCAG 2.2 Level AA. This statement explains how far we are, and how to tell us when something blocks you.

Privacy noticeTerms of useLicenceAccessibility

On this page

  1. Our commitment
  2. Conformance target
  3. Measures we take
  4. Compatible use
  5. Known limits
  6. The RavenFlo product
  7. Feedback and alternatives
  8. Review

Questions: privacy@ravenflo.io

Our commitment.

Enterprise software is used by people with a wide range of abilities. The marketing site should not be the barrier. We design pages with clear structure, visible focus, sufficient contrast, and text alternatives for meaningful images and diagrams.

Conformance target.

The target for ravenflo.io is Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. We run automated checks (including axe and Lighthouse) during development. A manual keyboard pass is part of ordinary review. A structured screen-reader pass with NVDA and VoiceOver is part of launch readiness; this statement will be updated when that pass is complete, including any remaining gaps.

Measures we take.

  • Semantic headings, lists and landmarks so that a page can be understood without sighted layout.
  • A “Skip to content” link as the first focusable control.
  • Visible focus styles on interactive controls, including on dark sections.
  • Text that meets contrast targets for body copy and primary actions.
  • Respect for prefers-reduced-motion: decorative motion and the feather drift stop when the system asks for less motion.
  • Forms with associated labels, required fields announced, and errors that can be read as text.
  • Diagrams and product drawings described in nearby text or accessible names; they are illustrations, not the only carrier of meaning.

Compatible use.

Pages are intended to work with current evergreen browsers and with keyboard-only navigation. The sticky product tour on the home page can be operated from the keyboard. Mega-menus open on focus as well as hover.

Known limits.

  • Some complex SVG diagrams compress labels on very small screens; a short text summary sits with those sections.
  • Third-party embeds are avoided on marketing pages. If one is added later, its accessibility will be called out here.
  • There is no video on the site yet. When there is, it will include a transcript, and captions for speech.
  • PDF downloads, when published, will be checked for a tagged text layer; until then, prefer the HTML whitepaper page.

The RavenFlo product.

This statement covers the public website. Accessibility of the RavenFlo applications that customers install is tracked separately with the product team. If you are evaluating the product for assistive-technology users in your organisation, ask during the demo so we can walk the current state honestly.

Feedback and alternatives.

If something on this website blocks you, write to accessibility@ravenflo.io. Please name the page and what you were trying to do. We will answer, and we will send the content in another form — for example plain text or a structured document — while a fix is made.

Security issues belong on the disclosure page, not this address.

Review.

This statement was published on the effective date shown above. We review it when the site structure changes materially, and after the launch screen-reader pass. Related pages: privacy notice, contact.

Last updated 11 November 2026. If a signed customer agreement says something different about the product, that agreement prevails for the product. These pages govern the website, and summarise the product only where they say so.

RavenFlo

Every message comes home.

The form could not be sent from this page. Refresh and try again.

Check the fields and try again.

Enter a valid email address.

Use your work email address. Personal inboxes are not accepted.

Consent is required before we can keep this request.

Too many attempts. Wait a few minutes and try again.

Product

  • Platform
  • Messaging
  • Calls and meetings
  • Board
  • Documents
  • Integrations
  • Control Tower

Security and deployment

  • Security
  • Trust centre
  • Responsible disclosure
  • Whitepaper
  • Deployment
  • Sizing guide

Solutions

  • Banking and financial services
  • Government and public sector
  • Healthcare
  • Manufacturing and energy
  • Conglomerates

Company

  • About
  • Careers
  • Partners
  • Blog
  • Contact
  • Request a demo

© 2026 RavenFlo

sales@ravenflo.io Privacy notice Terms of use Licence Accessibility security.txt