Skip to main content

​
Build apps that evolve from usage

GenieForge is the business to engineering translation layer. You describe who uses the app, what must happen, and what must never happen. GenieForge assembles, operates, and evolves the product from real usage. That is Living Software.

​
The loop in one glance

People use a project through the portal. Signals show friction. You approve the next plan and ship a version you can roll back. See How to use these docs.

​
Choose your path

I want to build my first app

One known-good prompt, Preview checklist, then invite.

I want to understand the architecture

Blueprint, project, portal, signals, and versions.

I want to invite customers

Portal invites, roles, and Preview as before go-live.

I want to connect another service

OAuth, inbound routes, HTTP, and custom domains.

I want to secure and launch

Access, Preview as, automations, domains, rollback.

I want to brief the AI better

Who, what happens, rules, and how you will know it worked.

​
Start here

How to use these docs

How to read these docs without treating them as a coding manual.

Controlling credits

Build vs Chat, active build time, predictable spend.

What GenieForge is

Category and differentiation from generated apps.

Apps, projects, and surfaces

Vocabulary for blueprint vs project vs portal.

​
Practice tutorials

Pattern walkthroughs drawn from real app shapes, with generic domain language you can swap for your own.

Meeting notes intelligence

Capture audio or notes; AI structures them; track action items and people.

Assigned work portal

Staff assign plans; participants run Today and upload proof for review.

Job OS with client portal

Internal pipeline, AI briefs, and a limited client portal for status.

Paycheck cash flow

Recurring expenses and debts mapped to a real pay calendar and forecast.

Ops exception board

Import metrics, score exceptions, clear a human review queue.

​
Get help