App Builder And Hosting

HivemindOS now offers a Replit/Lovable-style app-building experience with a local-first advantage: users can ask an agent to create and refine their app on hardware they already control, then purchase hosting only when the result needs to be shared or kept online.

This separates two jobs cleanly:

• App Builder drives adoption. Local and linked-machine creation, file operations, dependency installation, and loopback previews do not require a managed cloud agent.
• Hive Publish drives recurring revenue. HivemindOS operates the public route, release storage, access policy, renewal lifecycle, and isolated dynamic runtime.

For the product workflow, plan limits, and user-facing hosting lifecycle, see the App Builder guide.

Current Revenue Streams

Each charge applies to one Site. One customer can host several Sites, and a customer who builds entirely on their own machine can still buy any compatible hosting plan. This expands the paid funnel beyond users who need a Managed Cloud Agent.

Renewable plans use an opt-in auto-renew setting and debit the customer’s hosted credit balance every 30 days. A seven-day grace period protects an app from an immediate outage after a failed renewal, and a 30-day retention window gives the customer time to recover an expired or unpublished release. This is renewable hosting revenue, not a lifetime-hosting promise.

Role In The Revenue Model

Publishing is a concrete first paid activation. It lets a free local user pay HivemindOS for one managed outcome before the user needs a recurring control-plane subscription.

Retained publishers can later expand into Cloud Pro, Cloud Team, managed agents, models, APIs, and dynamic execution. Hosting is therefore an acquisition and expansion surface inside Hivemind Cloud, not a standalone company thesis.

Unit-Economics Boundary

The HivemindOS price is collected per Site, while Cloudflare’s base Workers subscription and included request/CPU allowances are shared at the account level. Current Cloudflare pricing starts with a $5 monthly account minimum, then meters additional requests and CPU at low unit rates. Dynamic Workers also meter unique workers invoked per day. See Cloudflare’s current Workers pricing and Dynamic Workers pricing.

The base platform and included allowances are shared across Sites, while storage, requests, CPU, logs, databases, support, payment processing, refunds, and taxes vary with real usage. Infrastructure gross margin must therefore be measured from production cohorts rather than inferred from a hypothetical portfolio.

The $1 preview should debit an existing hosted-credit balance or be bundled into a larger top-up. It should not normally create an isolated $1 card charge whose fixed payment-processing fee consumes a large share of the purchase.

Margin Protection

The Dynamic App plan now enforces 10 million requests, 250 million reserved CPU-ms, 1 million storage operations, and 1 GiB of runtime storage per Site. Every request reserves the full 25ms invocation ceiling, making the CPU budget conservative even when actual code usually finishes faster. Exhausted request or CPU allowances return HTTP 429 until reset; exhausted storage-operation allowances reject further calls, while capacity-limited writes fail closed without overwriting the prior value.

At current Cloudflare overage rates, a Site consuming its full conservative allowance remains bounded relative to its $25 plan revenue, even after the shared account allocation is exhausted. This replaces an unlimited tail risk with a known maximum; future published overage packs can create incremental revenue without silently passing through an unbounded bill.

Investor reporting should show hosted properties, conversion from preview to renewable hosting, 30/90-day hosting retention, revenue per property, infrastructure cost, payment cost, support cost, and contribution margin. Customer-count illustrations without conversion and churn assumptions are not forecasts.

Official prices, entitlements, renewals, credit debits, and public slug ownership remain server-authoritative. The open-source app can display and submit a plan, but it cannot redefine official hosting economics.