Year One: The First Month the Math Closed

On January 10, 2024, Helixrack recorded 20 active customers and the first month in which operating revenue exceeded the stated monthly operating cost. Five days later, the first customer reached one year in production.

The two events provided an early answer to different questions. Twenty customers suggested the facility could support its own monthly operation. One customer year provided a real period over which to compare service cost with an alternative—but only if the comparison disclosed what it included.

The month the operation covered itself

The canonical January snapshot records $2,240 in monthly revenue and $1,900 in monthly operating costs. The difference is $340, or roughly 15% of revenue.

That is an operating snapshot, not a claim of company-wide profit. It may not include capital purchases, debt, depreciation, taxes, financing costs, or every founder contribution. A final article must publish the accounting definition beside the number and reconcile the 20 active customers to contracts and invoices.

The average revenue implied by the snapshot is $112 per active customer. That average does not mean every customer paid the same rate. Equipment size, power, and service requirements differed, and promotional timing affected the first account.

The first customer’s twelve paid months

The first server was purchased December 10, 2022, received December 14, and moved into production on January 15, 2023. The historical first-month-free promotion applied to the intake and staging period before production. Paid service began at go-live.

At the $85 monthly rate, twelve paid production months through the first anniversary total $1,020:

Item	Amount	Treatment
Helixrack service	$85 × 12 = $1,020	Includes the stated monthly facility service
Server purchase	Pending invoice	Customer-owned asset; excluded from the $1,020
Customer labor and software	Not established	Excluded
Backup and ancillary services	Not established	Excluded unless supported by invoices

The canonical narrative also records an “equivalent AWS” figure of $14,400 for the year and a difference of $13,380. Those numbers are arithmetic, not yet a valid comparison. The cloud figure must be rebuilt from a dated AWS configuration and price record.

A transparent method would specify region, instance family and commitment, runtime, storage capacity and operations, data transfer, public addressing, backup, monitoring, support, taxes, and any compliance-related services. It would also decide how to account for the purchased R630, expected hardware life, replacement reserve, customer administration, and the different redundancy characteristics of the two options.

The $14,400 and $13,380 figures are presented as operating comparisons, not universal savings claims.

What the milestone established

Year one did not prove that owning a server is always cheaper than using cloud services. It showed that Helixrack had reached a customer count at which its stated monthly revenue covered its stated monthly operating cost, and that one customer had completed twelve paid production months on owned hardware.

It also set a higher standard for later claims. Customer count needs a dated ledger. Breakeven needs a defined expense boundary. Savings needs an apples-to-apples method. Retention needs a stated measurement period; this article makes no “zero churn” claim beyond the separately documented February 29, 2024 cutoff.

The math closed for one month. The next responsibility was to keep the definitions as reliable as the arithmetic.