Research to Reality.

Research
to Reality.

Engineering for the systems you run today, and the System after Next.

An OpenAFS read, in six steps 1. The client asks where the volume is; the database server answers the location lookup. 2. The client requests the file from the file server. 3. The database server's Protection Server supplies the user's groups for the permission check; the file server compares them with the directory's access control list. 4. The file server sends the file with a callback, a promise to notify the client if the file changes. 5. The client keeps it in its own cache. 6. Later reads come from that local cache with no network traffic while the callback holds. Database server Client + cache File server VL + Protection callback 1 2 3 4 5 6

One fetch; local reads while the callback holds.

  1. Where is it?
  2. Request
  3. Permission check
  4. File + callback
  5. Cached
  6. Local read

3D interactive

Interactive 3D visualisation, character design and digital-twin control centres.

Our approach

  • Maintain
  • Enhance
  • Develop
  • Predict

We maintain existing systems, enhance them, develop new ones, and predict what will be needed next.

OpenAFS spotlight

OpenAFS 1.8.16 is available

Our partnerships

  • IBM Platinum Business Partner
  • OpenAFS Foundation
  • AlmaLinux OS Foundation
  • SHARE
  • Open Mainframe Project

Latest news

Talk to an engineer

Contact us