2
1 Comment

You Should Always Be Able to Build

Two updates at NonBioS that we've been wanting to ship for a while - and a signal of where we're headed.

We've nearly doubled credits across all plans. This was made possible by infrastructure improvements we've been rapidly shipping, and it's not a one-time thing. Continuously expanding credits on every plan is now a directional commitment at NonBioS - we're investing heavily in our infrastructure so we can keep passing those gains directly to users. More headroom, more often.

One thing to note on models: nonbios-1.143 is now the default, labeled as the Premium Coding Agent. It's more powerful but consumes credits faster. If you want more mileage out of your credits, switch to the Standard Coding Agent (nonbios-1.137) when starting a new chat.

Second - and this one felt overdue - we've shipped Daily Credits. Running out of plan credits before your billing cycle renewed used to mean hitting a wall. That never felt right. You shouldn't lose momentum on a project just because you're between cycles.

So now every plan, including Free, falls back to a daily credit allotment that resets every 24 hours. When your plan credits run out, you keep going at a steady pace until your cycle renews or you top up. No lockouts, no surprises.

Taken together, these changes reflect a new way of thinking at NonBioS: you should always be able to build.

Full details at nonbios.ai/pricing - would love to hear your thoughts.

posted toAvatar for product NonBioS
NonBioS
  1. 1

    Nishant, "you should always be able to build" is a better brand line than anything on your homepage, and it means something for NonBioS that it does not mean for any other tool in this space. For a copilot, running out of credits just stops the suggestions. For an autonomous agent that runs long builds on its own machine, running out mid-task means the worker abandons the job halfway, on its own server. So Daily Credits is not billing generosity, it is continuity of an autonomous employee that does not get sent home in the middle of a deploy. That is the framing: you did not just remove a paywall, you kept the agent from quitting mid-build. Say it that way and a pricing update becomes proof of your actual positioning.

    One strategic caution, said as a friend. "Continuously expanding credits" is generous and users will love it, but credit generosity is a fight on infrastructure cost, and that is the one field where funded players can outspend you. Your moat is not more credits, it is that the agent finishes and ships on its own computer, which none of them do. So let the credits serve the moat rather than become the story: the reason to give more headroom is that an autonomous worker needs uninterrupted runway, not that you are cheaper. Cheaper is a race. Uninterrupted autonomy is a category.

    One concrete flag and a question. Defaulting new chats to the Premium 1.143 that "consumes credits faster" and then telling people to switch down to Standard for mileage sits a little against "always be able to build," because you are defaulting users toward the wall you just removed. For this brand, Standard as the default with Premium as the deliberate opt-in might fit the promise better. And the question the whole post turns on: when a user drops to daily-credit pace mid-build, does the agent keep working at the slower pace, or does it pause until reset? Steady pace is continuity. Pause is just a softer wall, and the difference is the entire promise.