Open-source · University-first

Stronger teams.
On your terms.

A shared space for university coaches and athletes to organize training, follow progress, and keep their institution in control.

Apache-2.0 softwareUniversity-operatedEnglish & العربية
Rugby practice on a grass field beside a university building in Dublin.
Built around life on and off the field.Stock photograph · Jonathan Borba / Pexels ↗

Your team. Your infrastructure. Your data.

Explore the source ↗

01 / Deployment

Open source. Institution owned.

Each university operates an isolated Rafik deployment. The software has no Rafik subscription; infrastructure and ongoing operations belong to the institution.

See self-hosting guide ↗
01

Start with the documented stack

A Unix server, Docker Compose, PostgreSQL, the API, web app and Caddy HTTPS.

02

Choose your infrastructure

Optional AWS, Azure and Google Cloud VM templates are unverified starters. Provider deployment and recovery checks remain for user testing.

03

Need help planning setup?

Ask about deployment assistance. Scope, region and operational responsibilities determine a quote. Managed hosting is not currently offered as a confirmed service.

Request a quote ↗

02 / Product

Less scattered work. More connected coaching.

Bring the day-to-day work of university sport into one institution-owned workspace.

01

Training with continuity

Build and publish programs, assign them to athletes, and review recorded sessions and performance assessments.

Read the guide
02

A clearer daily picture

Coordinate groups, appointments and attendance. Keep coach tasks and participant conversations close to the work.

Read the guide
03

An identity of your own

Set your institution’s name, logo and theme. Operate a separate deployment with your own users, files and backups.

Read the guide

Rafik is an evolving prototype. Institutional privacy, security and operational review are required before real athlete data. Current limitations ↗

03 / Docs

A practical place to begin.

From your first local instance to roles, workflows and day-to-day operations.

Explore documentation ↗