Build log

Building Forge64 in public

I’m building Forge64 so that one prompt becomes a real, hosted app: sign-in, a database, payments and a domain included, with hard caps so nobody gets a surprise bill, including me.

This page is the honest version of the changelog. An item appears here only once it is merged, with the commit that landed it. “Merged” means it is in the code and tested; “live” means it is deployed and verified in production. I don’t mix the two up.

    • Mergedafa176d0· W1aiarchitecturecost caps

      Every build now starts from a reference architecture

      I wrote down how experienced teams build 12 kinds of apps (SaaS, marketplaces, e-commerce, booking, streaming, fintech ledgers and more) as data, not prose. Your prompt is matched to up to three of them without a model call, so the architect starts from a proven design and your repo gets real architecture decision records. Research per niche is capped at $0.02 and every build has a hard $1 AI budget.

    • Merged0142ae70· Q3hostingdomainssecurity

      Custom domains with takeover protection

      Bring your own domain: it goes live only after we see both your TXT ownership token and the CNAME pointing at us in the same check. We re-check every 24 hours and drop the route if a record disappears, but a DNS outage never takes your domain down.

    • Merged6c21a175· L17enterprisesecuritysso

      Enterprise access is decided by the server, never the browser

      Every enterprise route now resolves who you are from your session and checks membership, role and plan on the server. An org id sent by the browser is only a selector. Enterprise SSO (OIDC and SAML) now uses DNS-verified domains.

    • Merged0eed83ef· Q2reliabilitytesting

      One command proves a prompt becomes a live URL

      `npm run accept:live` creates an app, deploys it, and passes only if a brand-new deploy reaches a working https URL. If it fails, it names the exact step that broke. It is credit-capped and refuses to run against production from CI.

    • Mergedeab4e058· Q15reliabilityrelease

      Staging first, gradual rollout, one-command rollback

      Merges now deploy to staging and run the live acceptance check before anything reaches production. Production rollouts go 10%, 50%, 100% and revert on failed health probes.

Release notes

From the changelog, with each feature’s current status.

  • · Available

    Guides for building any web app

    Twelve app types, five guides each: how to build it, the architecture, an example prompt, a security checklist and a scaling checklist, all taken from the reference architectures Forge64 plans against. Each guide says plainly that it is a reference design, not a list of what is generated today.

  • · Rolling out

    Selling with Forge Payments: guides and honest comparisons

    New pages explain how to accept payments in your app without setting up a payment account first, which countries sellers can be paid in, and how the fee compares with other creator-sales tools, including the cases where another tool is cheaper per sale. One all-in fee per sale (Free 13% + 30¢, Pro 9% + 30¢, Business 7% + 30¢, Enterprise per contract). Rolling out.

  • · Available

    Architecture playbooks and a stricter quality gate

    Forge64 now plans each app against one of 12 reference architectures before writing code, and records the decisions in the repo. A new deterministic gate checks every build for 21 kinds of defect, such as dead buttons, unauthenticated mutations and secrets in the client bundle, and sends blocking findings back for repair.

  • · Rolling out

    Forge Payments: get paid from day one

    Your app can take payments with verification and payouts to your bank account built in, with no separate payment account to set up. One all-in fee per sale (Free 13% + 30¢, Pro 9% + 30¢, Business 7% + 30¢, Enterprise per contract); refunds and disputes are handled with daily caps. Rolling out.

  • · Rolling out

    App AI Gateway

    Apps hosted on Forge64 can call Forge AI with the common chat-completions, messages and embeddings request formats, per-app keys, monthly caps and rate limits, billed from your credits. Keys only work from your server. Rolling out.

  • · Rolling out

    First-party analytics and error tracking

    Cookieless page-view analytics, uptime and response metrics for every app, plus error tracking that accepts the standard Sentry SDK envelope, all stored by Forge64. Rolling out.

  • · Rolling out

    Sleep and wake, static hosting and custom domains

    Idle apps on Free and Pro sleep and wake on the next visit, static sites are served without a container, and paid plans connect their own domains with DNS verification and automatic certificates. Rolling out.

  • · Rolling out

    One-click Google and GitHub sign-in for your app

    Generated apps can offer Google and GitHub sign-in through Forge64's shared broker, without registering OAuth apps. Codes are single-use, expire in 60 seconds and are bound to your app. Rolling out.

  • · Rolling out

    Video studio with posting to X and YouTube

    Forge AI drafts a promo video for your app, your browser renders it at no rendering cost, and you can post it to X or YouTube. Rolling out.

  • · Rolling out / Available

    Enterprise single sign-on and organizations

    Enterprise organizations can sign in with OIDC or SAML 2.0, manage members with roles and invitations, and verify a hash-chained audit log.

  • · Available

    Predictable pricing: hard caps on every meter

    Every metered resource now has a hard cap per account, app and plan plus platform-wide daily ceilings that refuse work instead of billing more. Paid plans add an overage spend cap you set; Free is never charged overage.