01 · about
a nonprofit software laboratory. anyone can bring a problem, teams collaborate and compete to solve it inside 24-hour build cycles, the community tries to break what gets built, square8 verifies it, and the software and the knowledge compound into a public commons.
02 · the thesis
the advantage is not cheaper labour. it is compressed time.
a conventional build for a mid-sized internal tool runs weeks to months. the same build, executed by a competent team directing modern tools against a locked specification, is a small number of 24-hour cycles. that compression is what makes every other mechanism here work.
it makes competition affordable — several teams on one problem is intolerable when losing costs three weeks, and entirely tolerable when losing costs a day. it makes breaking fast possible, because you can only afford an adversarial round if the build round was cheap. and it compounds: every build leaves connectors and components behind, so the next one starts further along.
if the median funded build takes more than three cycles, the thesis is not working and the pricing model has to be rebuilt around a different unit. median cycles-to-completion is therefore the single most important number here, and it is instrumented from build one.
measuring…
03 · what this is
a problem marketplace · a software-building network · a contribution and reputation system · an open-source commons · a verification layer · an adversarial testing program · a nonprofit technology laboratory · an education system for problem solvers.
fiverr · upwork · a software agency · a bootcamp · a hackathon · an AI app builder · a social network · a VC fund · a CSR vendor.
square8 is not a listing board that connects two strangers and takes a cut. it operates the layer underneath the work, and the take rate reflects operated infrastructure rather than matchmaking.
04 · the money
funded in full before work starts, released on acceptance, divided by a policy that is versioned in the database. the row that applied to any payout can be read back years later.
| % | share | why it exists |
|---|---|---|
| loading the live policy… | ||
commons & education pays for the academy, learning infrastructure, public-interest builds and open-source grants. the people shipping software here pay for the people learning to ship it. that is what the nonprofit structure is for.
the attack pool and the verification share do not accrue to square8. they pay the security researchers who break the build and the people who audit it. founders receive no automatic percentage of any project.
05 · the price
a build cycle is 24 hours of wall-clock time in which one team delivers a demoable increment against a locked specification. human-hours survive only as an internal scoping aid and as the conventional comparison. they are never the unit of sale.
price = base cycle rate × cycle count × complexity × integration
× risk × urgency × demand − reuse discount
every coefficient is a row. nothing below is hardcoded, and none of it should be defended on the basis that it is written down — these are starting assumptions with the right shape, replaced by measured values as builds complete.
| factor | value | what it means |
|---|---|---|
| loading… | ||
06 · governance
today founders operate the laboratory — treasury, disputes, verification, moderation, policy. the rules are published even when the decisions are unilateral.
later, community governance expands into treasury allocation, build policy, reputation rules, opportunity caps, moderation and grants.
it means nobody extracts. founders receive no automatic percentage of any project. they may be compensated for work actually performed, through governed mechanisms, and that governance tightens as the organisation grows.
07 · open
listings, teams, attack findings, verification verdicts, escrow states, payout rows and the policy version behind each one — read-only to anyone, over the same api this site uses.
every pricing coefficient on this page is a live row. change one and every estimate on the site moves with it.
four static pages and a handful of modules. the logic that matters lives in database functions.