Friday Code lifetime deal

Historical tiers: pay for capabilities before project counts

Tier 1 was $139 with 50 monthly credits and 100 projects. It lists JavaScript and HTML applications and no custom agents. That makes it a restricted starting point, not a cheaper version of every higher-tier capability. A high project count is of little use if each project needs more iteration than the credit pool allows.

Tier 2 was $429, with 250 credits, 500 projects and 10 custom agents. The founder confirms OpenRouter BYOK from this tier. For a solo builder needing broader languages and a way to pay for additional model usage directly, this is the meaningful historical baseline.

Tier 3 was $999 with 500 credits. The founder identifies integrations and automations among the differences from Tier 2. Tier 4 adds team support for up to 5 members and 1,000 credits. Only buy team capacity for actual collaborators, after checking permission and spending controls.

Tier 5 was $2,799, with 1,500 monthly credits, 5,000 projects, 500 custom agents and up to 20 team members. None of these historical options can currently be purchased through the sold-out listing.

The offer was for brand-new users only, explicitly excluding previous accounts, trials and paid plans. Activation was required within 60 days; upgrades were allowed while the deal was live and downgrades within 60 days. If the offer returns, check its new eligibility terms before creating a trial account, rather than assuming that testing first preserves eligibility.

Why 250 credits do not mean 250 completed changes

Friday charges for agent work, including model use and actions. The founder explains that a longer assignment can make many calls and that separate requests can trigger separate deductions. Current documentation directs users to the agent selector for live rates. There is no dependable universal conversion from credits to apps, pages or hours.

A useful evaluation is one complete workflow: add a form, save its data, show errors and verify permissions. Count the initial generation, corrections and final checks together. A cheap first draft followed by repeated repairs may cost more than a larger first run. The credit allowance does not translate into a fixed number of finished apps.

Top-up bundles are available in billing and the documentation says purchased top-up credits do not expire. Auto-refill can trigger further purchases when a balance falls. The current public documentation does not provide a complete top-up price schedule, so treat that as an unresolved cost before enabling automatic purchasing. Monthly included credits and purchased credits should be tracked separately.

Separate the builder bill from the application bill

BYOK means you supply an OpenRouter key and pay for that provider usage. It is useful for model choice or continuing work after the included allowance, but it does not make inference free. Confirm the selected route before a long task: a Friday agent balance and your external provider balance are different budgets.

Publishing a database-backed app can also involve a domain, hosting, database capacity, email delivery and payment processing. An integration makes those services easier to connect; it does not prove their paid plans or usage are prepaid. For a low-traffic prototype, free service allowances may suffice. For customer-facing use, price the intended traffic, storage and transactional email separately.

Keep an export and a recovery path outside the desktop project folder. The ability to keep source code reduces dependence on the editor, but recreating deployment settings, secrets and databases still takes work. Do not put live customer data into a generated app until someone has checked access controls and backup restoration.

Shared credits need a spending agreement

In the Tier 5 question, the founder says teammates cannot see each other’s projects but can see the shared team credits. At that time, per-user credit caps were not available; the reply promised them later. A promised control is not a verified current feature.

Before adding collaborators, establish who may start long-running work and who can enable top-ups. A team allowance is not a guaranteed private budget for every member. If enforceable individual spending limits are mandatory, ask the vendor to demonstrate them on the exact current lifetime plan.

Compare the current subscription separately from the old lifetime offer

Friday’s public pricing currently lists Pro at $20 per month with 100 monthly credits and Max at $100 per month with 500. A year at those listed monthly rates is $240 or $1,200 before extras. These are subscription examples, not equivalent replacements for particular AppSumo tiers: the founder explicitly says the lifetime plans do not map one-to-one to Pro or Max.

It would therefore be misleading to divide the old lifetime price by a rival’s monthly fee and call the result guaranteed savings. Compare the required integration, team controls, model access and workload first. Since the lifetime offer is sold out, the current decision is whether the available subscription or another tool is appropriate—not whether to buy the historical discount.

Friday Code or Fuzen: decide who should host and maintain the app

Choose the Friday Code approach when editable source files and your own deployment path matter. It suits projects that may move to a developer or another editor later. The trade-off is that somebody must understand enough about the finished application to maintain and verify it.

Fuzen is closer to a managed business-application service: its templates and hosted database can reduce setup for an internal CRM or operations tracker. Its AI and runtime allowances remain capped, and it cannot export a standalone source-code application. If a spreadsheet and a simple form already support the process, keep that free setup until the missing workflow justifies a builder.