Sign in

Downloads

Coming soon, and nothing to download yet.

There is a Credda client for desktop and for phones. It is in development, no build of it has been released for any platform, and this page is not going to pretend otherwise: every row below is off, and none of them will carry a link until there is a real file at a real address behind it.

What does work today is the GitHub Action. It runs Credda in your own CI, it needs nothing installed on your machine, and it is the path this site documents in full.

01Platforms

Five platforms, none of them released.

The line under each platform says what the client repository builds today, read out of it on 2026-09-21. It is a statement about source. None of it is a build you can obtain, which is why every control here is disabled rather than hidden: a row that quietly disappeared would leave you guessing whether the platform is supported at all.

  • macOS

    Not yet available

    :desktopApp:packageDistributionForCurrentOS produces a DMG, and only when it is run on a Mac. Nothing signs it and nothing publishes it.

  • Windows

    Not yet available

    The same packaging step produces an MSI, and only when it is run on Windows. There is no cross-build, so a Windows installer has to be cut on a Windows machine by hand.

  • Linux

    Not yet available

    The same packaging step produces a DEB on a Linux host. The desktop client itself runs: :desktopApp:run opens the window, and the shared test suite executes on this target.

  • Android

    Not yet available

    :androidApp:assembleDebug produces an installable debug-signed APK. Debug-signed is not a release build, and no release build has been cut or published.

  • iOS

    Not yet available

    The shared framework links for device and simulator, and a CI job boots a simulator, installs the app and checks that it renders. A build for a real phone needs an Apple Developer Program membership, which Credda does not have yet, so there is nothing to put on a device or in TestFlight.

No version, no file size and no checksum appears anywhere on this page. There is nothing released for any of those to describe, and a plausible-looking one would be a number this site invented.

02Instead

Run Credda in your own CI today.

The Action is the shipped path and it asks for no download. You add one workflow file to a repository and Credda runs on GitHub’s runners, inside your own CI, with no copy of your code leaving it.

One file
.github/workflows/credda.yml, referencing Credda-io/action@v1. The whole block, with every permission it asks for and why, is on the install page.
What the app would have been for
The client is a read-only triage surface: what Credda found, what is waiting on a person, and what it declined. It starts no runs and changes no code, so nothing on this page is blocking you from using the product.
Install the ActionThe workflow, in full

03When it ships

The waitlist is the only list there is.

There is no separate list for the app. Credda has one early-access waitlist, it lives on the contact page, and it stores an address and nothing else on our own infrastructure. We write to it once, when Credda opens.

Join the waitlist