Skip to content

Real software built by Ileen

Real builds, not demos.

Ileen has generated production-usable software from technical briefs, worked across existing codebases, and deployed applications to cloud environments. Below is the library of public case studies. Earlier projects may be anonymised; P-Secretary links directly to its public source repository.

Autonomous build. Human-controlled release.


Headline cases

These three are the proof points to start with. They cover the full delivery chain: design the architecture, build the code, deploy to production.

01 — An open-source personal secretary, built end to end

P-Secretary: an open-source personal secretary →

A self-hosted assistant for email, WhatsApp and Telegram, with PostgreSQL-backed workflows, background workers and a web dashboard. Its public repository includes the implementation, operational documentation and explicit boundaries for agent actions.

end-to-end build · public source · Docker + PostgreSQL · human-confirmed actions


02 — Codebase → Live GCP in <10 minutes

Deploy Mode: Sports platform on Cloud Run →

Existing Next.js + Supabase + Stripe app with an AI coaching service. Ileen analysed the codebase, detected 13 missing secrets, provisioned them in Secret Manager, deployed to Cloud Run and validated HTTP 200 — then guided a non-technical user through every third-party account setup.

<10 min active deploy · 13 secrets provisioned · HTTP 200 validated


03 — Turn a codebase into a content brief

Content Mode: Nutrition App Briefing →

A repository was ingested and turned into a structured product briefing, ready for content creation — a different example of Ileen supporting work beyond implementation.


All case studies

Design Mode

Design + Build

  • P-Secretary → — Open-source personal secretary built end to end with Ileen.

Develop Mode

  • P-Secretary → — A complete application and public repository delivered from requirements.

Deploy Mode

Content Mode


How to read these case studies

Every case study follows the same structure so you can compare them like-for-like:

  1. At a glance — facts and numbers up front.
  2. The brief / project — what the user actually asked for.
  3. What Ileen produced autonomously — concrete artefacts, no abstractions.
  4. What required human action — explicit, not hidden.
  5. Honest limitations — what the system cannot do today.

This is not marketing. It is documentation of real work. If you find a claim that looks impressive but is not traceable to an artefact, please flag it.