Open for work · one fractional seat free, Q3 2026
Prague · est. 24 May 2016 · IČO 05108438

Agentic software,
shipped with twenty
years of taste
behind every commit.

Banana Pancakes is a one-person Prague studio. Four products of its own — Polarix, HOCR, Perdify, Worklist — plus fractional CTO and agentic software work for teams that need a senior engineer who already knows how the agents behave.

Operator
Jiří Zajpt, jednatel
Shipping since
May 2016 — ~10 years
Writing code since
~2005 — ~20 years
Products live
3 live · 1 in beta
Based
Prague 5, CZ — CET
§ 01 — Products

Four things I built.

All owned 100% by Banana Pancakes s.r.o. No outside investors.
/ 01 · iOS puzzle game Live · App Store

Polarix

A merge-puzzle iOS game with one mean twist: opposite charges fuse, same types merge up to annihilation. Slide cores, set up chains, survive — three rules, infinite depth.

playpolarix.com Swift · SwiftUI
/ 02 · B2C call-center CRM Live · Sales-led

HOCR

A B2C CRM built around the call center. Sales pipeline, e-sign agreements, Twilio Flex routing, branded customer portal, and AI-driven call QA — one audit-friendly platform, ready to launch in days.

hocr.app Rails · Rust · Twilio Flex
/ 03 · iOS, in private beta Beta · TestFlight

Perdify

A consumer iOS app in closed TestFlight. 400+ registered players as of this spring — still sharpening the core loop before opening the gate.

TestFlight Swift · Rails · Postgres
/ 04 · Encrypted task manager Live · worklist.app

Worklist

Zero-knowledge, end-to-end encrypted task management for teams that actually care who sees what. Tasks, comments, delegations, attachments and notes — all encrypted client-side, before they leave the browser.

worklist.app Rust · TypeScript
§ 02 — Open source

Things I’ve given away.

Extracted from real apps. Issues welcome.
/

runledger

Rust PostgreSQL SQLx 4 crates
github.com/featherenvy/runledger

A Postgres-native durable job queue and workflow orchestrator for Rust. Cron schedules, workflow DAGs with dependency counters, idempotent enqueue, dead-letters, panic-aware metrics rollups, and external workflow gates — extracted from a real production app and published as a standalone four-crate workspace.

runledger  ·  workspace
├─ runledger-core            public contracts, traits, types
├─ runledger-postgres        SQLx persistence · queue · DAG
├─ runledger-runtime         worker · scheduler · reaper
└─ runledger-test-support    ephemeral DB harness for tests
§ 03 — Services

Three ways I plug in.

Most engagements run 3–12 months. Retainer or fixed scope.
01 / Fractional CTO

Fractional CTO

I take the technical seat at your table. Architecture, hiring, codebase triage, board updates — handled by someone who has shipped the thing four times over, under his own name.

01Engineering roadmap & hiring plan
02Architecture review & decisions
03Weekly standing call with founders
04On-demand code & PR review
03 / Growth

Honest growth

Landing pages that load fast and say something true. Paid acquisition with real attribution. I run the numbers and tell you when the spend isn’t working — before you ask.

01Landing pages & A/B testing
02Paid: Google, LinkedIn, Meta
03SEO & technical content
04Attribution & weekly readouts

For twenty years I’ve led teams of developers and shipped products. Running a team of agents across projects asks the same skills. Software ships at breakneck speed now — the challenge is making it correct, and maintainable.

— On running engineers, and agents Jiří Zajpt Jednatel & principal engineer, since 2016
2016
founded · 24 May · Prague
4
products · 100% owned
~20
years writing software
1
engineer · solo operator
§ 04 — Stack

Tools I reach for.

Languages I’ve led teams in — and lead agents in too.

Principles

Typed where it helps. Boring where it must. Fast where it matters.

Agents are great at volume and terrible at judgment. I pair them with languages whose type systems catch the mistakes agents love to make — Rust, TypeScript, Swift — and keep a clear path back to sanity when they wander.

/ 01Rustbackends · hot paths
/ 02TypeScriptfrontends · tooling
/ 03Ruby on RailsCRUD · backoffice · MVPs
/ 04SwiftiOS · Polarix & Perdify
/ 05Pythonresearch · ML · glue
/ 06Postgresthe database
/ 07Codexprimary driver · Claude for UI
/ 08Grafanabusiness dashboards · alerts
§ 05 — How I work

A short, predictable dance.

Every engagement roughly follows this shape — adjusted, not invented.
Phase 01
First call

45 minutes to understand the business, the team, and what’s on fire. I’ll tell you if I’m the right shop — and if not, who is.

~ 1 week
Phase 02
Written proposal

Scope, cost, timeline — in a short document you can share with a co-founder or a board without explaining it twice.

~ 1 week
Phase 03
Ship & iterate

Weekly demos, a shared Linear board, and a principal who answers Slack. No status-update theatre, no middleman.

3 – 12 months
Phase 04
Handover (or stay)

When the thing is built, I document everything and leave — or stay on a lighter retainer. Your call, not mine.

open-ended
§ 06 — Contact

Tell me what’s broken
or missing.

Short messages are fine. I reply within a working day, in plain Czech or English. No form-letters, no sales cadences — it’s just me.

Signal / Phone
on request
Registered office
Na pomezí 910/2
Jinonice, 158 00 Praha 5
Česká republika
Company
IČO 05108438
DIČ CZ05108438
C 258440, MS v Praze
Základní kapitál 147 060 Kč