Skip to content

Enterprise

Deployed your way, governed your way.

Yakini is set up for each organization with our team: where it runs, how people sign in, who sees what, and how it fits the way your teams work.

Rollout plan

Tandala Financial

  • DeploymentHosted with a private runner
  • Sign-inSAML 2.0 single sign-on, required
  • AccountsSCIM 2.0 from the directory
  • ModelsChosen per task, self-hosted for code
  • ApprovalsDefinitive verdicts held for approval
  • OnboardingGet started: 4 of 6 steps done
Sample dataOne organization’s choices, made with our team.

Deployment

Four ways to run Yakini.

The same product and the same controls in each: choose what your security requirements call for.

How a private runner works
  • Hosted

    We run Yakini for you. Connect your tools and choose your models; there is nothing to install.

  • Hosted with a private runner

    Audits run inside your network. Repository code and test execution stay there; only the audit record and result, reduced by your outbound policy, come back.

  • Dedicated

    A deployment of Yakini for your organization alone, run by us.

  • Self-hosted

    Run Yakini in your own environment with your own PostgreSQL, object store and models: Kubernetes with Helm, Docker Compose or systemd, with Terraform for the Helm chart.

    • Kubernetes with Helm
    • Docker Compose
    • systemd
    • Terraform for the Helm chart

Identity and provisioning

People arrive and leave through your directory.

Sign-in follows your identity provider, and accounts follow your directory, so access stays current without manual work.

  • Single sign-on with OIDC or SAML 2.0, routed by your verified email domains
  • Just-in-time accounts with group-to-role mapping
  • SCIM 2.0 provisioning and deprovisioning; leavers’ sessions end at once
  • Single sign-on can be made mandatory, keeping break-glass password access for owners who use an authenticator app
  • Multi-factor authentication with an authenticator app
Sample dataDirectory groups mapped to Yakini’s built-in roles.
Sample dataA team’s settings, each showing where its value comes from.

Governance

Rules you set once, applied everywhere.

Roles, approvals and settings follow your organization’s structure, and every change to them is recorded.

  • 13 built-in roles over 44 permissions, plus custom roles, scoped to the organization, a business unit, a team or a project
  • Approvals where they matter: definitive verdicts before publication, and comments or issues written back to your tracker
  • Settings that inherit from organization to business unit, team and project, with overrides and a view of where each value comes from
  • Configuration as code: export, preview and publish the whole configuration, with a version history
  • Rules and automation, privacy profiles, and members who can always see which people-related features are on

Onboarding

A guided start, step by step.

Guided setup connects each tool with plain instructions, checks every key before saving it, and can hand a step to a colleague who has the access. Get started then shows what is left, worked out from your data, so nobody ticks boxes.

Operating-model presets give sensible defaults to start from, and a first check of recent work shows where delivery stands from day one.

Organization setup

Get started

4 of 6 done

  1. Connect your toolsWork tracking, source control and CI/CD connectedDone
  2. Confirm your projectsOne project has no repository yetNeeds a look
  3. Bring in your peopleSingle sign-on and SCIM are set upDone
  4. Set up your teamsEvery team has a leadDone
  5. Choose how you workAn operating-model preset was appliedDone
  6. Check your recent workAsked of an engineering directorTo do
Sample dataEach step’s status comes from the organization’s own data.

Pricing

How pricing works.

Yakini isn’t sold from a price list. Pricing is tailored to each organization and set out in a written proposal, once we understand how you would deploy and use Yakini.

Tell us about your teams, your tools and where Yakini would need to run. We’ll come back with a proposal that covers it.

Procurement

Your review, your terms.

We work through your security review and data-processing terms.

Plan your rollout with us.

Tell us how your teams work and where Yakini would need to run. We’ll show it with a sample organization and go through deployment, identity and governance.

  • Hosted, dedicated or self-hosted
  • Your choice of models, self-hosted too
  • Pricing set out in a written proposal