jikobi.com
Menu

Private builds

Build it. Test it. Keep the proof.

jikobi.com builds your code from the exact revision you pick. Each build runs in its own sandbox and ends with the files, the full log and a SHA-256 for every file.

Ask about access See how it works

Windows x64 first. Nothing is free and sign-up is closed: building stays inactive until it is priced, then we switch it on account by account.

Your builds this morning (example)

Shop app · Windows x64 · DoneCommit 8f31c2a. 2 files, each with its SHA-256.
Shop app · v1.5.0 · RunningBuilding. You can leave this page.
Billing worker · main · FailedStep 3 of 4 failed. The log shows why.

Three steps. No build server to keep.

You say what to build. We run it in a clean place and hand you the result.

  1. Add your project

    Name the GitHub repository and the branch to build. We set up the build steps with you.

  2. Pick a revision

    A branch, a tag or a commit. We record the exact commit that was built.

  3. Get the files and the proof

    Download the files. Each one has its size and SHA-256, next to the full log.

Why you can trust a result

A green tick is not enough. You get what ran, from which commit, and what came out.

The exact commit

A branch moves. We record the commit SHA we really built, so you can build it again later.

A fresh sandbox each time

Every build gets its own workspace with limits on memory, processes and time. It is deleted when the build ends.

A hash for every file

Each file a build makes gets a SHA-256. Check it after you download.

The full log

Read every step, including the one that failed. Logs stay after the workspace is gone.

No tokens in the dashboard

You never paste a password or a token here. Repository access is set up with you, once.

Queue time is free

We count only the minutes your build really runs, per second.

What you will not have to do

The slow, fiddly parts are ours.

  • Keep a build machine patched and running
  • Install and update compilers and build tools
  • Guess which commit a file came from
  • Clean up full disks after old builds

Developer and operations

Our developer and operations tools. jikobi.com builds your code; CI/CD.ee ships it to your servers; Backanator keeps the data safe.

CI/CD.ee Safe releases to your own servers, for any stack. Backanator Database backups you can see and trust. Jikobi (this site) Build it. Test it. Keep the proof.

Questions

What can it build?
Projects on GitHub, built for Windows x64 first. A recipe is data, the app's own file pins the exact tools and sources, and the first recipe builds a Windows installer. Other targets and stacks are added one recipe at a time.
What about Windows and Android?
Windows x64 is the first target. Android and Linux come later, each with its own price and its own recipe.
Where does my code go?
We fetch the revision you picked into a temporary workspace for one build. The workspace is deleted when the build ends, whether it worked or not. We keep the log, the file names, sizes and hashes, and a receipt for every build. The files stay as release assets.
Do you need my GitHub token?
Not in this dashboard. It refuses tokens, keys and URLs. Access to a private repository is set up with you when we switch on building for your account.
Does it work today?
Not yet. Sign-up is closed and building is inactive until it is priced. When it is on for your account the dashboard says so; until then it shows no builds, because none have run.
What does it cost?
Nothing is free. Building is inactive until it is priced; build minutes are then metered per second and queue time is not counted. See pricing.

Ask about access

Building is inactive until it is priced. Ask about access and we tell you when it is on.

Talk to us Ask a question