One core · two front doors

A fair-credit research loop.
Open, and inside the company.

CrowdSota is one core: a fair-credit contribution ledger plus an AI research loop, where people contribute tokens, compute, or ideas. That same core powers two products of equal weight.

CrowdSota Open

Public science, aimed at published SOTA

Anyone can join the public lab. Contributions go on a public ledger, with credit that can become authorship. The aim is crowd-sourced research that reaches published SOTA.

Join the open waitlist

CrowdSota for Enterprise

A year-round internal innovation engine

Leadership sets strategic goals and attaches budgets. Anyone, across team lines, can contribute at any time. Fair, visible credit — and the strongest work can be funded as real products.

Explore the enterprise door

Fundraising site · Launch target 22 November 2026 · Product not yet built · View the pitch deck

The problem

The work can run all year. Credit, and the hackathon, do not.

The same gap shows up in public research and inside companies: people and agents can already do the work, but credit, access, and funding still sit in closed rooms, or in a once-a-year burst.

In open science

Closed rooms, thin credit

AI agents can already search literature, run experiments, and draft papers. The tools often live in a private workspace. Decentralized networks may reward GPUs or tokens, which is not authorship. Open-science platforms welcome people, but are not built for bring-your-own keys or agents on a public ledger.

Inside companies

Weekend toys, or one heavy week a year

Internal hackathons are either lightweight individual exercises that do not take on large problems, or serious annual events that are effort-heavy and then go dark. Teams work in silos. There is often no direct, ongoing incentive, and leadership cannot see how AI spend maps to strategic goals — across, for example, a company with 100 teams of about five people working independently.

How it works

Three ways to contribute. One ledger. Two settings.

The loop is the same in CrowdSota Open and CrowdSota for Enterprise. People contribute tokens, compute, or ideas; a fair-credit ledger records the work. In Open, that ledger is public. In Enterprise, it is visible across team lines, inside the company.

Tokens

Bring a key, or fill the pool

Use your own model API key for a single run (BYOK), or donate credits to a shared pool that others can draw from. The ledger records which path funded the work.

Compute

Run a worker on your GPU

A lightweight worker picks up queued experiments. Samples are spot-checked by re-running them elsewhere, so a contribution is not just a claim — it can be checked.

Ideas, code, reviews

Shape the science

Propose a question, ship code, or review a result. Human judgment sits beside agent work, and both are attributed.

Fair credit

Two layers, then authorship — in public or across the company.

Credit is not a vibe and it is not only a token balance. We separate measurable effort from evidence of impact, and we map people (and agents) onto standard contributor roles when a result is written up. In Open, the ledger is public. In Enterprise, the same rules make credit visible across team lines.

Effort layer

Tokens spent, GPU-hours contributed, runs completed. This layer answers: who showed up, and with what resources?

Impact layer

Runs that move a stated benchmark score count more than runs that do not. This layer answers: whose work changed the result?

When a project is written up, authorship follows the CRediT taxonomy (an ANSI/NISO standard): roles such as Conceptualization, Software, Validation, and Writing — not a single undifferentiated byline.

Example — illustrative only, not live data

Contributor Type Effort Impact CRediT role
A. Chen ideas Hypothesis + protocol Accepted into challenge #1 Conceptualization
@gpu-node-14 compute 18.4 GPU-hours, 12 runs 3 runs improved the score Investigation
R. Okonkwo tokens BYOK, 4 agent reviews Caught a failed spot-check Validation
credit-pool tokens Shared credits, 2 runs No score move Resources

Names and figures in the table are fictional examples to show how the ledger would read. They are not traction.

CrowdSota Open

A public lab, aimed at published SOTA.

Anyone can participate. Contributions of tokens, compute, and ideas go on a public ledger, with fair credit that can become authorship. The long-term aim is crowd-sourced research that reaches published state of the art — we will not claim a SOTA result until one exists.

01

Open participation

You do not need to be at a frontier lab. Researchers, contributors, and sponsors can join a public challenge and be named for the work they actually did.

02

A public contribution ledger

Effort (tokens, GPU-hours, runs) and impact (runs that move a benchmark score) are both visible. When a project is written up, authorship follows CRediT roles.

03

Toward published results

The point is not a token balance. It is a shared, checkable record of research that can be reviewed, reproduced, and, if it earns it, published.

CrowdSota for Enterprise

A year-round, always-on innovation engine.

Leadership defines big strategic goals and attaches budgets — tokens, compute, funding, and recognition. Any employee or team, across organizational silos, can contribute ideas, experiments, code, or compute at any time. The ledger gives fair, visible credit across team lines. The strongest contributions can be funded to become real products.

Goals & budgets

Leadership sets the problems

Strategic goals stay in view all year, not only during a hackathon week. Budgets travel with the goal, so people can keep making progress when the idea is ready — not when the calendar says so.

Across silos

Anyone can contribute, any day

A contribution can come from any team, not only the team that “owns” the problem. Credit is visible across team lines, so work is not trapped in a local hero’s weekend project.

Incentives

Direct credit, then real funding

The ledger is the incentive: effort and impact are named. Top contributions and projects can be funded for implementation as products — continuously, not as a once-a-year prize.

For leadership

See how AI spend maps to goals

Because tokens, compute, and outcomes sit on the same ledger as the stated goals, leadership gets a live view of where AI spend is actually going — and what it is moving.

From the founder — workplace experience, not a customer claim

Amazon, as experienced

Internal hackathons were fine for people to join as individuals. They were weekend-scale, “toy” exercises. They were not a way to solve large problems.

Toyota, as experienced

The annual hackathon is serious: the top five products get funding to be implemented as products. It still happens once a year, and standing it up takes a lot of effort.

CrowdSota is meant to automate that into a continuous, year-long hackathon, with direct incentives, so anyone in the company can make progress at any time. It is also meant to break silos — for example, in a company with 100 teams of about five people working independently today. Amazon and Toyota are mentioned here only as places the founder has worked, not as customers or design partners.

Enterprise roadmap proposed

What companies will need, when we build this

The first enterprise version is planned to add controls that a public lab does not need. These are roadmap items, not shipping features.

SSO Private deployment / data controls Audit trail

Why now

The pieces exist. The continuous lab does not.

The research observations below are from sources we reviewed in November 2026, not market-size claims. The enterprise framing is founder experience, not a survey.

  • Autonomous research is entering the scientific record. Sakana’s AI Scientist work was published in Nature in March 2026, including a discussion of credit, watermarks, and the limits of generated papers.
  • Researchers are already buying agent workbenches — mostly private ones. 2026 Product Hunt launches such as OpenScience, Meshia, and ClawsGO Science show demand for AI research agents and, in Meshia’s and OpenScience’s case, bring-your-own keys or wallets. They are not public contribution ledgers.
  • Permissionless compute contribution has been demonstrated. Prime Intellect’s INTELLECT-2 described a globally distributed RL run in which heterogeneous machines could contribute, with verification of inference work.
  • Contributor roles already have a standard. CRediT is an ANSI/NISO taxonomy of 14 roles, designed so research outputs can name kinds of work, not only an ordered author list.
  • Inside companies, the serious version is still annual. From the founder’s time at Amazon and Toyota: many internal hackathons stay individual and toy-scale; the serious ones fund real products, but only once a year and at high operational cost. A year-round loop with a fair-credit ledger is the gap we want to close. This is lived experience, not a market statistic.

How we’re different

One core. Two gaps we have not seen filled together.

For CrowdSota Open: open participation, BYOK plus a shared credit pool, agents that do research work, and a public fair-credit ledger. Adjacent products cover some of these, not all. This comparison is from a November 2026 review of public pages, not a paid landscape study.

CrowdSota planned Meshia / OpenScience Sakana / FutureHouse / Autoresearch / Orikata Bittensor / Prime Intellect ResearchHub / Zooniverse
Open participation Yes — public lab Private team workspaces Single-team systems Open for compute / mining Open to people
BYOK + shared credits Yes — key per run or pool BYOK / wallet / credits in-product Typically hosted or single-team Compute and token rewards Not built around model keys
AI agents doing research Yes — queued experiments Yes Yes Training / inference, not paper authorship Human review or classification
Provable fair credit Public ledger + CRediT No public contribution ledger found Ordinary internal or paper credit Emissions for work, not CRediT authorship Open, but not agent + BYOK credit

For CrowdSota for Enterprise, the contrast is not that public table. It is the difference between a weekend or annual hackathon and a continuous, funded challenge with a ledger that crosses team lines. We are not naming other internal-innovation vendors here; we have not done a paid landscape study of that category.

Roadmap

Stand up the core. Open a public bench. Pilot inside a company.

22 November 2026

This site and the waitlist

A public pitch, a pledge form, and conversations with researchers, contributors, sponsors, investors, and companies interested in a pilot. The product is not live yet.

Next proposed

First open benchmark challenge

One narrow, measurable public task. Waitlist pledges of keys, GPU-hours, and ideas are invited to join.

Then proposed

The ledger, workers, and spot-checks

A visible log of tokens, GPU-hours, and runs — including BYOK versus pool. GPU workers pull queued experiments. A sample of runs is re-executed to catch bad results.

In parallel proposed

First enterprise pilot

An always-on internal challenge tied to a leadership goal and a budget, with credit visible across team lines. Top work can be put forward for product funding.

Enterprise needs proposed

SSO, private deployment, audit trail

Single sign-on, private deployment and data controls, and an audit trail — the controls companies will need before this runs on internal work.

Aim proposed

Impact credit, write-ups, and funded products

Score moves feed the impact layer. Open results can be authored with CRediT roles; the long-term aim is published SOTA, claimed only if it exists. Inside a company, the corresponding aim is that the best work is funded as a real product.

Pitch deck

Twelve slides. On this page.

Use the arrows, the keys ← →, or fullscreen. Placeholders for the raise and the founding team are marked in gold. Open and Enterprise have equal weight.

Pitch · 22 November 2026

CrowdSota

One core: a fair-credit contribution ledger plus an AI research loop, where people contribute tokens, compute, or ideas.

Two equal front doors — CrowdSota Open, a public lab aimed at published SOTA, and CrowdSota for Enterprise, a year-round internal innovation engine.

CrowdSota

01 / 12

Problem

The work can run all year. The credit system cannot.

  • In research: agents exist, but labs, keys, and credit often stay closed.
  • Inside companies: hackathons are weekend toys, or serious but once a year.
  • Silos keep ideas, compute, and credit inside one team. Leadership cannot see how AI spend maps to goals.

CrowdSota

02 / 12

Solution

One core. Two front doors, equal weight.

  • The core — a fair-credit ledger and an AI research loop: tokens, compute, ideas.
  • CrowdSota Open — a public lab, a public ledger, authorship via CRediT, aimed at published SOTA.
  • CrowdSota for Enterprise — an always-on internal engine: leadership goals and budgets, credit across team lines, top work funded as products.

CrowdSota

03 / 12

How it works

Tokens. Compute. Ideas. Same loop, two settings.

  • Tokens — bring an API key per run, or donate to a pool (or a company budget).
  • Compute — run a worker; queued jobs; sample re-runs for checks.
  • Ideas / code / reviews — humans steer, agents execute, both are named.
  • In Open the ledger is public. In Enterprise it is visible across team lines.

CrowdSota

04 / 12

Credit model

Effort, then impact, then named roles.

  • Effort — tokens, GPU-hours, completed runs.
  • Impact — runs that move a stated score or goal count more.
  • Authorship / recognition — CRediT roles on a public write-up, or visible credit across teams inside a company.
  • Spot-checks make compute claims testable.

CrowdSota

05 / 12

CrowdSota Open

A public lab aimed at published SOTA.

  • Anyone can contribute tokens, compute, or ideas.
  • Every contribution is recorded on a public ledger, with fair credit.
  • When a result is written up, authorship follows CRediT roles.
  • The aim is crowd-sourced research that can be published. We will not claim SOTA until it exists.

CrowdSota

06 / 12

CrowdSota for Enterprise

From a weekend or an annual event to a year-long challenge.

  • At Amazon, as the founder experienced it: internal hackathons were individual, weekend-scale “toy” exercises — not a way to solve large problems.
  • At Toyota, as the founder experienced it: the annual hackathon is serious, and the top five products get funding to be implemented — but it is once a year, and effort-heavy.
  • CrowdSota automates that into a continuous, year-long hackathon, with direct incentives, so anyone can make progress at any time, including across silos.
  • Leadership sets goals and budgets, and gets a live view of how AI spend maps to those goals. Amazon and Toyota are prior workplaces, not customers.

CrowdSota

07 / 12

Why now

The parts are here. The continuous lab is not.

  • AI-scientist systems are in the literature (Sakana, Nature, March 2026).
  • BYOK research workbenches launched in 2026 (e.g. Meshia, OpenScience).
  • Permissionless compute contribution has been shown (INTELLECT-2). CRediT already standardizes roles.
  • Inside companies, the serious format is still typically annual — from founder experience, not a market survey.

CrowdSota

08 / 12

Landscape

Adjacent in two markets. Equivalent in neither.

  • Open: Meshia / OpenScience — agents + BYOK, private workspaces. Sakana / FutureHouse / Autoresearch / Orikata — single-team scientists. Bittensor / Prime Intellect — compute rewards. ResearchHub / Zooniverse — open, not agent + BYOK ledgers.
  • Enterprise: the contrast is weekend or annual hackathons, and internal work that does not carry fair credit across team lines.
  • We have not done a paid landscape study of internal-innovation vendors, so we do not name a competitive set there.

CrowdSota

09 / 12

Business model · proposed

Enterprise, the open platform, and sponsored challenges.

  • Enterprise subscriptions and paid pilots.
  • A platform fee on pooled credits on the open platform (not on a contributor’s own BYOK key).
  • Sponsored benchmark challenges.
  • These are proposed. We have no revenue yet.

CrowdSota

10 / 12

Go-to-market · proposed

One public challenge. One enterprise conversation.

  • Open a waitlist for researchers, contributors, sponsors, investors, and companies.
  • Collect pledges of tokens, GPU-hours, and ideas for a first, narrow public benchmark with a public ledger.
  • In parallel, talk to companies about a year-round internal pilot tied to a real leadership goal.
  • Enterprise controls — SSO, private deployment and data controls, an audit trail — are on the roadmap.

CrowdSota

11 / 12

The ask

We are raising [Raise amount TBD]

To fund the ledger, the first open challenge, early enterprise pilots, and a small product-led team. Details of use of funds will follow the amount.

Team: [Founders]

CrowdSota

12 / 12

← → keys

Waitlist & pledges

Reserve a place — in the open lab, or for a company pilot.

Tell us who you are and what you might contribute, or if you want to talk about an enterprise pilot. This is a pledge of interest, not a contract and not a sale of tokens or equity.

This is a pledge of interest, not a binding commitment.

Investors

If you want to talk about the raise, use the button. It opens the waitlist form with your role set to Investor.

Request a conversation