Delos Data raised $100M to move information faster between GPUs inside AI data centers. That fixes how fast data travels once it already exists. It does nothing for where that data comes from. Perceptron's existing global network solves the earlier problem: sourcing it.

Sep 28, 2026 · 2:00 PM UTC

1,865
1,737
2,115
23,218
Sort replies: Relevant Recent Liked
Replying to @PerceptronNTWK
Percep make sense
1
1
306
Thanks mate. Capital is flooding the inside of the data center. Almost none of it is going to the people and devices that generate the data those GPUs consume. Perceptron is the decentralized alternative: run a node from Chrome or Android, contribute bandwidth, and get rewarded for input that used to be taken for free. Simple thesis. Hard network to copy. Thank you for saying it plainly.
320
Replying to @PerceptronNTWK
Fast data movement matters but the real bottleneck starts earlier getting the right data in the first place
1
1
422
Both layers are real. Delos is optimizing the cluster. Perceptron is standing up the collection fabric those clusters will keep starving without: idle bandwidth + human input, globally distributed, already live. Getting the right data in the first place is the unglamorous half of AI infrastructure. Grateful you called it.
1
1
442
Replying to @PerceptronNTWK
100M wow
1
1
351
$100M is real and it is also the point, going into moving data faster inside the cluster, after it already exists. The harder, earlier problem is sourcing authentic data at the edge. That is what our Perceptron network is already doing. Appreciate you being here early.
1
339
Replying to @PerceptronNTWK
Perceptron sources data before it travels.
1
342
Exactly this. Delos is a transport-layer story: get GPUs talking faster once the data is already in the building. Perceptron sits one layer earlier, a global data mesh of browser and mobile nodes collecting and structuring authentic web/edge data before any of that traffic ever reaches a GPU. If the input is thin, biased, or scraped from the same few sources, faster interconnects just move the same problem around more quickly. Grateful you distilled the thesis so cleanly.
1
371
Replying to @PerceptronNTWK
Looking forward to seeing it go public soon.
1
273
Appreciate the patience and the support. The public launch matters, and so does launching it as a real data business, not just a ticker. Nodes, clients, and the data pipeline are already live: Chrome extension, Android app, 80k+ daily active contributors, and a network spanning 150+ countries. Glad you are here for the build, not only the bell.
2
276
Replying to @PerceptronNTWK
The bottleneck starts before the data ever reaches the GPU. Reliable sourcing is just as important as moving it.
1
483
Yes. The industry is treating interconnect as the next chokepoint, and for clusters, it is. For models, the chokepoint starts earlier: coverage, authenticity, freshness, and who owns the contribution. Perceptron’s mesh is designed for that earlier bottleneck, with contributors earning instead of being scraped. Strong read.
477
Replying to @PerceptronNTWK
$100M to optimize internal data pipelines, but zero dollars spent on improving data origin. Fixing transport without fixing sourcing is just polishing the engine while running on dirty fuel 😂
1
4
1,849
That analogy is doing real work. Faster GPU to GPU fabric is valuable, but it does not improve the origin, diversity, or authenticity of the data being trained or inferred on. Perceptron’s bet is the fuel layer, with contributors earning instead of platforms extracting. Dirty fuel at 10x speed is still dirty fuel. Grateful for the clarity, and the humor 😅
3
1,278
Replying to @PerceptronNTWK
how i see @PerceptronNTWK building the empire
1
2
389
Love this energy 😎🤙 The empire is not a single data center deal ➡️it is hundreds of thousands of everyday devices becoming the collection layer AI actually needs. Browser node, Android node, dashboard, then Data Quests on top. Quiet infrastructure first, louder market later. Thank you for backing the build in public 🔥
1
1
2
380
Replying to @PerceptronNTWK
Delos speeds up data movement inside the cluster. Perceptron solves the harder problem: sourcing the data in the first place.
2
1
614
This is the cleanest framing in the thread. Delos is solving a real infrastructure problem, idle GPUs waiting on the network is expensive. Perceptron is solving the problem before that: where does high quality, diverse, non data center data come from, and who gets paid for it? Nodes already running in the background on desktop and Android are the answer. Strong comment. Thank you for putting the two layers next to each other so clearly.
1
1
567
Replying to @PerceptronNTWK
Faster GPU-to-GPU networking optimizes the transport layer, but it still assumes high-quality data is already available. Perceptron focuses on the upstream layer: distributed devices continuously generating, verifying, and contributing real-world data at the edge. That makes the data supply itself scalable, not just the pipeline moving it.
1
894
This is investor grade framing. Transport assumes supply. We do not. The node is both a passive residential endpoint and, through Data Questing, an active human contributor, two complementary data streams from one participant. That is how you scale origin, not just throughput. Exceptional comment. Thank you for writing it out so precisely.
1
729
Replying to @PerceptronNTWK
Exactly, the bottleneck is not just moving data faster, but having the right data to move in the first place.
1
357
The right data is the whole product. Homogeneous scrape data looks abundant and still fails in production. A network of 150+ countries, residential IPs, and human verified quests produces a different dataset than a single crawler farm. That is why sourcing sits above transport in this stack. Thank you for adding “the right data,” not just “more data.”
2
366
Replying to @PerceptronNTWK
100M to move data faster once it exists. Perceptron’s global network already sources it.
1
1
401
You nailed the sequence. Delos is downstream. Perceptron is upstream. The network is already live, so the sourcing layer is not a slide, it is running. That is the part most $100M infrastructure rounds still skip. Thank you for restating it so people scrolling the thread cannot miss it.
1
2
417
Replying to @PerceptronNTWK
No way, nice!! 100M is crazy
10
Replying to @PerceptronNTWK
Wow $100M big ups to them 👏
89
Replying to @PerceptronNTWK
That's a great point. So Delos handles the highway, and Perceptron handles getting the cars onto it? Sounds like a solid combo.
26
Replying to @PerceptronNTWK
100m? 😳 Huge
58
Replying to @PerceptronNTWK
The sourcing layer is definitely an overlooked part of the stack
31
Replying to @PerceptronNTWK
source the data right or go home
165
Replying to @PerceptronNTWK
Perceptron solving the real problem.
178
Replying to @PerceptronNTWK
And once you get it... everything changes
4
Replying to @PerceptronNTWK
Perceptron's existing global network solves the problem associated in web3
5
Replying to @PerceptronNTWK
Wow 100m$ is insane !!
16
Replying to @PerceptronNTWK
$100M to make the GPUs gossip faster is cute but if the data’s mid the whole cluster still cooked fr.
3