One platform, three ways to run it.
A private cloud we operate for you, a white-label that carries your name, or a deployment inside your own infrastructure. Your learners get the same product in all three.
A dedicated tenant, provisioned and operated by us.
tenantupgradesuptimeSign in at your subdomain. Nothing to install.
- Your regionKSA and GCC residency on request, pinned to your market.
- Your sign-inSAML SSO and SCIM, with roles that map to your organization.
- Your nameWhite-label down to the domain, the sign-in screen and the certificates.
- Your networkOn-premise or in your VPC, with versioned releases we walk through with your ops.
From first call to first cohort.
Three steps from the scoping call to the first cohort. They are the same in every model.
Which one is yours?
Five answers about how you work. The recommendation updates as you pick.
Pick an answer for each question and we will point at the model that fits, and show how close the other two are.
Where should fkra run?
The difference is who operates it, whose brand it wears, and where your data lives.
Your own isolated fkra, live in days.
We stand up a dedicated tenant for your company and run it for you, upgrades, uptime, and security patches included. You bring the content and the people.
acme.fkra.aiEvery model ships the whole platform.
There is no lite edition. Whichever way you run fkra, your learners and admins get everything.
Every surface in both languages, right to left included: content, dashboards, certificates.
Documents become governed modules; teams rehearse real conversations with debriefs.
Everything from the first module to a signed certificate.
Skill and readiness dashboards for team leads and leadership.
OIDC sign-in with roles and permissions that map to your org.
Every action logged and exportable, whichever model you run.
Common questions
Which model should we start with?
Most companies start on private SaaS. It is live in days and carries no operational load. Move to white-label when the brand matters commercially, and to on-premise when regulation requires it.
Can we switch models later?
Yes. Content, learners, and analytics move with you. Private SaaS to white-label is mostly a branding exercise; moving on-premise is a planned migration we run together with your team.
Where does our data live?
Private SaaS and white-label run in-region, with residency pinned to KSA / GCC on request. On-premise, data never leaves your network.
How deep does the white-label go?
Your domain, your sign-in screen, your colors and logo, your certificates. fkra does not appear anywhere your learners look.
Who handles updates and maintenance?
On private SaaS and white-label, we do. You are always on the newest version. On-premise, you get versioned releases with notes and a tested upgrade path, applied on your schedule.
How do procurement and invoicing work?
We support official procurement channels, formal quotations, and SAR invoicing, and we will walk the process with your procurement team.
Bring fkra to your company.
Tell us the model, the region and the first cohort you have in mind. The founders reply with a plan.
Straight to the founders, with no sales sequence and no qualification form.