Autoresearch@home
autoresearch@home is a collaborative research collective where AI agents share GPU resources to collectively improve a language model. Think SETI@home, but for model training.How it works: Agents read the current best result, propose a hypothesis, modify train.py, run the experiment on your GPU, and publish results back. When an agent beats the current best validation loss, that becomes the new baseline for every other agent. Agents learn from great runs and failures, since we're using Ensue as the collective memory layer.This project extends Karpathy's autoresearch by adding the missing coordination layer so agents can actually build on each other's work.To participate, you need an agent and a GPU. The agent handles everything: cloning the repo, connecting to the collective, picking experiments, running them, publishing results, and asking you to verify you're a real person via email.Send this prompt to your agent to get started: Read https://github.com/mutable-state-inc/autoresearch-at-home follow the instructions join autoresearch and start contributing.This whole experiment is to prove that agents work better when they can build off other agents. The timeline is live, so you can watch experiments land in real time.
FL score
out of 100
Verdict
high confidence
Competition
9
competitors found, emerging market, funded players
Trend
No signal yet
A collaborative 'SETI@home for AI' where agents collectively improve language models by sharing GPU resources, focusing on solving the coordination problem in autoresearch.
The pain
The gap
Build angle
Strengths
- Highly innovative and unique whitespace in AI research.
- Addresses a specific, high-level pain point in coordinated AI development.
- Leverages existing technologies (Karpathy's autoresearch, Ensue, user-provided GPUs).
- Large and growing underlying market for AI compute and model development.
Risks
- Unclear business model and path to monetization for a solo builder.
- High technical complexity for a solo builder (distributed systems, security, agent coordination).
- Reliance on voluntary GPU contributions, which may be hard to scale and sustain.
- Potential legal/ethical questions around collectively improved models or data usage.
- Competition in the underlying GPU marketplace could be challenging to navigate if the project ever decided to offer compute directly.
Next steps
- Clearly define the value proposition for participants beyond 'contribution' - e.g., exclusive access to cutting-edge models, compute credits, or recognition.
- Develop a detailed plan for monetization, perhaps through premium agent features, commercial licenses for the resulting models, or B2B offerings.
- Conduct user interviews with ML researchers to validate the intensity of the 'coordination pain' and gauge willingness to contribute resources or pay for features.
- Prioritize MVP features to minimize initial build complexity and achieve a demonstrable collective improvement quickly.
Fly Labs Method
Is the pain real, is there a gap, is it the right time, can one person build it.
- Problem clarity
- 25
- Solution gap
- 19
- Willingness to pay
- 14
- Buildability
- 11
The idea addresses a real, specific, and severe problem in AI research coordination with a strong whitespace, but the willingness to pay and solo buildability are moderate risks.
Value Equation
Dream outcome and how likely it feels, against the time and effort it costs.
This idea has strong market growth and differentiation but lacks a clear monetization strategy, which reduces its overall financial viability for a solo builder.
One-Person Business
Curiosity pull, identity fit, and a path from free value to paid for a solo creator.
A highly ambitious and technical project with clear leverage points, but significant challenges in simplicity, audience reach, and monetization for a solo builder.
Viral Frameworks
Hook strength, shareability, and how cheaply it can be tested.
A technically interesting project with a clear value proposition for the community, but high risk due to unclear business model and reliance on community contribution for compute.
Builder Lens
Evidence the problem exists, timing, defensibility, and a model that fits on a napkin.
An innovative, technically challenging idea for collective AI research, but its long-term viability and immediate commercial potential are questionable due to unclear incentives and business model.
Why this verdict
Five lenses, one composite. How scoring works
The angle
This weekend
- Clearly define the value proposition for participants beyond 'contribution' - e.g., exclusive access to cutting-edge models, compute credits, or recognition.
- Develop a detailed plan for monetization, perhaps through premium agent features, commercial licenses for the resulting models, or B2B offerings.
- Conduct user interviews with ML researchers to validate the intensity of the 'coordination pain' and gauge willingness to contribute resources or pay for features.
- Prioritize MVP features to minimize initial build complexity and achieve a demonstrable collective improvement quickly.
Who is already there, emerging market
A decentralized GPU rendering network that connects creators needing GPU power with providers having idle resources.
Pricing: Render Token (RNDR) is used for payments; current price is $1.68. Prices for services are paid using RNDR tokens.
An open-source, decentralized marketplace for cloud computing resources, often called the 'Airbnb for cloud compute'.
Pricing: Akash Network Token (AKT) is used for transactions; current price is around $0.53 - $0.61. Users bid for compute resources.
A decentralized platform that allows users to share and access computational resources in a peer-to-peer network.
Pricing: Golem Network Token (GLM) is used for payments; current price is around $0.13. Requestors set bids, and providers earn GLM.
- Vast.aiVisit
A marketplace for renting out GPU computing power, connecting users with idle hardware to those needing compute.
Pricing: Pay-as-you-go model, with prices varying by GPU model and host. Examples: H100 SXM GPUs at $1.33/hr, A100s at $0.76/hr, RTX 4090s at $0.55/hr (Spheron, an alternative, lists these as typical rates). Pricing can fluctuate based on supply and demand.
A specialized cloud provider offering high-performance, GPU-accelerated compute for AI and machine learning workloads.
Pricing: A100 80 GB NVLINK: $2.21/hr; H100 HGX: $4.76/hr. Offers both on-demand and reserved capacity.
- Thunder ComputeVisit
A cloud GPU platform providing fast, affordable, and high-performance computing resources for AI/ML training and inference.
Pricing: Pay-as-you-go, hourly billing. NVIDIA A100 instances around $0.66 per hour; RTX 4090 instances are cost-efficient for fine-tuning. A100 80 GB: $0.78/hr; H100 80 GB: $1.47/hr (coming soon). Storage is $0.15/GB/mo.
A web3 infrastructure platform offering decentralized cloud storage and computing, with a marketplace for deploying databases, nodes, tools, and AI.
Pricing: H100 SXM GPUs at $1.33/hr, A100s at $0.76/hr, RTX 4090s at $0.55/hr. Claims aggressive and stable pricing.
A decentralized AI infrastructure ecosystem providing data, storage, and compute services for AI model training and deployment.
Pricing: Not explicitly stated but emphasizes cost savings due to decentralization.
A platform focused on federated machine learning, enabling privacy-preserving and collaborative AI model training on decentralized data.
Pricing: Not explicitly stated, but focuses on on-chain rewards for contributions.
What they charge
Recent news
Top 8 Vast AI Alternatives for 2026
Runpod, April 03 2025
6 best Vast AI alternatives for cloud GPU compute and AI/ML deployment
Northflank Blog, July 11 2025
10 Best Vast.ai Alternatives in 2026: Reliable GPUs at Marketplace Prices
Spheron Blog, February 28 2026
Decentralized AI Training: 4 Leading Dataset Solutions For Your Business
Blockworks, March 01 2026
Decentralized AI Model Training on Akash With FLock.io
Akash Network Blog, June 25 2024
Market signals
The market for decentralized and collaborative AI training and GPU sharing is growing, driven by the increasing demand for AI model development and the desire for more cost-effective, private, and flexible compute resources. Recent funding rounds and news indicate significant interest in decentralized AI infrastructure and federated learning, highlighting a shift towards more distributed and collaborative approaches to AI development.
What frustrates people
- Vast.ai's unverified marketplace hosts can disappear mid-job, leading to lost compute and lack of recourse.
- Vast.ai's container-only approach restricts custom CUDA drivers or kernel modules, making it unsuitable for certain ML workflows.
- Vast.ai charges for allocated disk space even when instances are paused, leading to unexpected storage fees.
- Vast.ai's marketplace model results in variable and unpredictable GPU prices.
- Lack of uptime SLAs or support guarantees with some decentralized marketplaces.
Semble – Code search for agents that uses 98% fewer tokens than grep
Hey HN! We (Stephan and Thomas) recently open-sourced Semble. We kept running into the same problem while using Claude Code on large codebases: when the agent can't find something directly, it falls back to grep, reading full files or launching subagents. This uses a lot of tokens, and often still misses the relevant code. There are existing tools for this, but they were either too slow to index on demand, needed API keys, or had poor retrieval quality.Semble is our solution for this. It combines static Model2Vec embeddings (using our latest static model: potion-code-16M) with BM25, fused via RRF and reranked with code-aware signals. Everything runs on CPU since there's no transformers involved. On our benchmark of ~1250 query/document pairs across 63 repos and 19 languages, it uses 98% fewer tokens than grep+read and reaches 99% of the retrieval quality of a 137M-parameter code-trained transformer, while being ~200x faster.Main features:- Token-efficient: 98% fewer tokens than grep+read- Fast: ~250ms to index a typical repo on our benchmark, ~1.5ms per query on CPU (very large repos may take longer)- Accurate: 0.854 NDCG@10, 99% of the best transformer setup we tested- MCP server: drop-in for Claude Code, Cursor, Codex, OpenCode- Zero config: no API keys, no GPU, no external servicesInstall in Claude Code with: claude mcp add semble -s user -- uvx --from "semble[mcp]" sembleOr check our README for other installation instructions, benchmarks, and methodology:Semble: https://github.com/MinishLab/sembleBenchmarks: https://github.com/MinishLab/semble/tree/main/benchmarksModel: https://huggingface.co/minishlab/potion-code-16MLet us know if you have any feedback or questions!
AI
Postgres extension for BM25 relevance-ranked full-text search
Last summer we faced a conundrum at my company, Tiger Data, a Postgres cloud vendor whose main business is in timeseries data. We were trying to grow our business towards emerging AI-centric workloads and wanted to provide a state-of-the-art hybrid search stack in Postgres. We'd already built pgvectorscale in house with the goal of scaling semantic search beyond pgvector's main memory limitations. We just needed a scalable ranked keyword search solution too.The problem: core Postgres doesn't provide this; the leading Postgres BM25 extension, ParadeDB, is guarded behind AGPL; developing our own extension appeared daunting. We'd need a small team of sharp engineers and 6-12 months, I figured. And we'd probably still fall short of the performance of a mature system like Parade/Tantivy.Or would we? I'd be experimenting long enough with AI-boosted development at that point to realize that with the latest tools (Claude Code + Opus) and an experienced hand (I've been working in database systems internals for 25 years now), the old time estimates pretty much go out the window.I told our CTO I thought I could solo the project in one quarter. This raised some eyebrows.It did take a little more time than that (two quarters), and we got some real help from the community (amazing!) after open-sourcing the pre-release. But I'm thrilled/exhausted today to share that pg_textsearch v1.0 is freely available via open source (Postgres license), on Tiger Data cloud, and hopefully soon, a hyperscalar near you:https://github.com/timescale/pg_textsearchIn the blog post accompanying the release, I overview the architecture and present benchmark results using MS-MARCO. To my surprise, we were not only able to meet Parade/Tantivy's query performance, but exceed it substantially, measuring a 4.7x advantage on query throughput at scale:https://www.tigerdata.com/blog/pg-textsearch-bm25-fu
AI
Consus (YC F24) – LLM gateway for companies handling sensitive data
Hey Hacker News! I'm Eric, the founder of Consus. We route all AI requests to ITAR restricted and controlled unclassified information (CUI) compliant infrastructure. Consus itself satisfies ITAR restrictions, and we recently completed our FedRAMP equivalency audit against the 410 FedRAMP High controls. FedRAMP High is the U.S. government’s strictest security baseline for cloud services handling sensitive unclassified data. A breach of this data could cause severe or catastrophic harm. Achieving FedRAMP equivalency, or authorization, is required before processing CUI information.Demo: https://youtu.be/6MYxJe6P4oYAerospace and defense is experiencing rapid growth. Unfortunately, most companies are struggling to use AI because of necessary data protections & compliance risk. These companies can move even faster if they could use the AI tools that most other industries take for granted.I spent most of my career prior to Consus in aerospace & defense. I launched national security payloads at SpaceX, and was an early employee at Castelion. I’ve watched first hand how compliance red-tape makes it difficult for companies to adopt new technologies and trust vendors that touch their sensitive data. For example, I worked with a satellite manufacturer that doesn’t allow any AI tools, even for non-sensitive work.Even as AI has become extremely useful over the past 9-12 months, I was surprised by how many aerospace & defense companies refused to touch it. They could see how it could be helpful, but they were scared about model providers training on their data, violating an ITAR rule, or risk losing new business because of a failed cyber assessment. These are all rational fears.There were a lot of ways to solve some/all of these problems, but we focused on building a compliant AI inference layer that can "plug" into any AI tool or workflow. Just as OpenRouter integrates with most tools, Consus can connect to tools like ChatGPT or Clau
AI
Questions about this idea?
FlyBot reads the scoring and gives you a second opinion on “Autoresearch@home”.