Keep your product moving.
Ongoing feature development and improvements through Studio, for a fixed monthly fee. We agree on priorities with you, put coding agents to work, and review and test the results before release.
Swipe for approvals and current work
See progress, current work, and the decisions that need your input in one place.
Follow each piece of work from proposed scope through implementation, review, and acceptance.
Give requirements, reference documents, and notes a shared home alongside your project.
Swipe for more results
Review test scenarios, findings, and the evidence behind a delivery decision.
Keep track of preview and production environments, releases, and their status.
Look back through approvals, changes, and delivery milestones in the project history.
Keep your product moving with ongoing development for a fixed monthly fee. One engineering lead and one account manager are assigned to your project: your lead directs the engineering and reviews the work; your account manager keeps priorities, communication, and planning clear.
Pancake Studio gives the work a shared home for scope, decisions, progress, and review. When your project no longer needs active development, move it into maintenance so the software continues to receive attention.
Ongoing feature development and improvements through Studio, for a fixed monthly fee. We agree on priorities with you, put coding agents to work, and review and test the results before release.
When active development winds down, switch to maintenance at a lower monthly fee. Submit bugs for us to fix while we keep dependencies current and regularly scan the codebase for defects.
We agree on the monthly fee and engagement details with you before starting. The Studio portal is in development.
Discuss your project ↗What should the software do, who is it for, and what is getting in the way? Bring an idea, an existing product, or a problem worth solving.
We agree on a fixed monthly fee and initial priorities, and assign your engineering lead and account manager before work begins.
Your engineering lead directs the agents and reviews the results. Your account manager keeps you informed and coordinates priorities as the work progresses.
Continue active development while there is more to make. When the project is ready for ongoing care, move to maintenance for bug fixes, dependency updates, and regular defect scans.
$ find frontend/ admin-panel/ -iname "*.tsx" | xargs cat | wc -l
78980
$ find crates/ -iname "*.rs" | xargs cat | wc -l
377899
$ git log --reverse --format="%ai" | head -1
2026-02-13 18:24:49 +0100 # first commit
$ date
Sat Apr 25 22:40:10 CEST 2026 We bet on Banana Pancakes’ agentic development approach and got the work of five engineers in the first month — with the judgment to tell us when we were wrong. Startup speed, senior taste, zero hand-holding. Hire them before someone else does.
An AI interrogation mystery for iOS. Six suspects think, remember, and lie on their own. Question them by voice or text and find the killer before the room turns on you.
Zero-knowledge Git hosting. The client encrypts code before push and decrypts it after pull; the server stores ciphertext. HushGit staff cannot read repository contents, and a server breach exposes ciphertext rather than plaintext.
An iOS merge puzzle. Opposite charges fuse, while matching cores merge until they annihilate. Slide cores and set up chain reactions.
A B2C CRM for call centers, combining a sales pipeline, e-sign agreements, Twilio Flex routing, a branded customer portal, and AI-driven call QA. HOCR can go live in days.
Zero-knowledge, end-to-end encrypted task management for teams. The browser encrypts tasks, comments, delegations, attachments, and notes before upload.
Menstrual cycle tracking for iOS. Cycle data, symptoms, and notes stay on the device by default, encrypted with AES-256-GCM. PrivaCycle has no developer-operated server. Encrypted iCloud sync, decoy mode, and a panic-erase code are available.
Behind Pancake Studio
Our engineering experience shapes how we direct agents, review their work, and decide what is ready to ship. These tools and skills make that practice repeatable across projects.
Gives agents the context, commands, and checks they need to work reliably in every project.
Explore jig-shOur engineering practice, written for agents. Focused skills guide planning, code review, refactoring, and privacy checks, with clear standards for the evidence behind each result.
Explore jig-skillsThe foundation for our Rust backends, designed from the start with developers and coding agents in mind.
Explore batterDesigned to guide agents through implementation, review, and verification, with people setting direction.
Explore epicdI’ve led software teams for twenty years. Agents changed who types the code, not who chooses the design, sets the checks, and rejects bad work. Shipping is faster; responsibility still sits with the engineer.
Active development covers the agreed feature work and improvements, engineering direction, project coordination, implementation, review, testing, and releases. Maintenance covers bug fixes, dependency updates, and regular codebase scans for defects. We agree the scope and fixed monthly fee with you before starting.
During active development, your engineering lead directs the technical work, guides coding agents, and reviews the results. Your account manager coordinates priorities, planning, and communication. You set the business goals and help decide what matters next.
Yes. We can develop an existing product as well as start a new one. We first review its current state, how it is tested and released, and what you want to change. That gives us a basis for agreeing the starting priorities and engagement.
We agree priorities with you in a shared backlog, considering business value, impact on users, technical risk, and dependencies between tasks. Your engineering lead explains the trade-offs; your account manager keeps the agreed order clear as needs change.
When your project no longer needs ongoing feature work, it can move to maintenance at a lower fixed monthly fee. We agree the transition and care priorities with you. If substantial new work comes up later, we can discuss a return to active development.
You submit a report describing what happened, what you expected, and who is affected. We investigate, prioritize the issue by its impact and risk, implement a fix, and test it before release. Dependency updates and regular defect scans also help identify work beyond reported bugs.
Tell us about your project and whether you need active development or maintenance. A short outline is enough. We’ll discuss the work, the monthly fee, and how to get started. Czech or English is welcome.