Загрузка видео...

Не удалось загрузить видео

На главную

Internet Computer introduced OpenSaaS, but what is it? Internet Computer (DFINITY Foundation) introduced OpenSaaS today, and it's become a major topic of conversation in its ecosystem. Given the huge traction, it makes sense to dive into what the feature means for ICP... What is OpenSaaS? As the name implies,...

BSCNews's profile picture

BSCN

1,371,605 subscribers

19,992 просмотров • 4 дней назад •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

Dear ICP community, the Internet Computer has now been running strong for 5 years 👏👏👏 Here is a celebratory preview of ICP "cloud engines," the sovereign frontier cloud technology the network shall soon provide from Main points: — Cloud engines enable anyone to spin up their own sovereign frontier cloud. The technology involves an extraordinary inventive step, in which cloud is created from a mathematically secure network of nodes. The nodes run as part of the Internet Computer network ( but are selected and configured by the cloud engine's owner. — The frontier cloud provided by engines is strongly focused on enabling AI agents to build and update online applications and services for us. The world is changing fast, and nearly all new online apps and services are already being built with the help of AI, and thus cloud engines target the future of cloud. — Software hosted on cloud engines is tamperproof, which means that it is immune to infrastructure hacks, because it runs inside a mathematically secure network protocol, rather than on computers directly. This means that AI agents, and those building with them, don't need to have a security team in the loop, or to trust someone else's security team. This is crucial, because in the future, non technical people will demand the freedom to build with full automation — where they just need to issue instructions to AI about what to build, and don't need to worry about anything or anyone else. Of course, apps and services running on engines are also vastly safer from the new breed of hacker being enabled by frontier AI. (The cloud engines themselves are also "tamperproof." Even if a hacker gains physical access to some portion of a cloud engine's nodes, and can make arbitrary changes, the computations and data of the hosted apps and services cannot be corrupted or interrupted so long as the network's fault bounds aren't exceeded. The recent hack of Vercel, a major cloud platform, which gave hackers access to the apps it hosted, provides additional perspective on the importance of this advantage.) — Software hosted on cloud engines is guaranteed to run, so long as a sufficient number of the engine's nodes are running. This means that AI can build applications and services without the need to have a human systems admin team constantly tinkering with the underlying platform to keep it running, which is again crucial, because in the future, non technical people will expect the freedom to use AI to build without the support of others. — New frontier programming language technology, in the form of the Motoko language developed by Caffeine Labs, leverages seminal "orthogonal persistence" technology that unifies program logic and data to deliver further unlocks for AI (Motoko is the first computer language being developed that targets agents that are writing software rather than humans engineers per se). Nowadays, AI can build and update production apps at a prodigious rate, even at the speed of conversation. But it can also make mistakes, and there's a risk that an update it creates might be "lossy" in the sense it causes some transformed data to be lost. Again, in this new world, it's both undesirable and impractical for everyone to have to have a systems admin team on-hand to detect lossy updates and roll them back, but Motoko provides a solution: it can detect new software updates are lossy before they are applied, reducing potentially catastrophic errors by AI to harmless coding retries. — Software hosted on cloud engines is "serverless" but unlike traditional serverless software, directly it directly incorporates data through "orthogonal persistence." Another key purpose is simplify backend software logic and fuel the modeling power of AI by increasing abstraction (sorry for the technical language!!!). Put simply, this enables AI to produce more sophisticated backends, faster, and at dramatically lower costs, as measured by the number AI API tokens consumed during coding. (Tip for the technical: orthogonal persistence is a new paradigm where "the program is the database," and data lives inside program variables, which is possible because it's as if hosted software runs forever in persistent memory). — An expanding database of skills at shall make it possible to develop and directly deploy apps and services to your cloud engines directly from Claude Code, Perplexity, Codex and other AI platforms. Further, your account on can be connected, so that new apps and updates created through conversation automatically appear hosted from your cloud engine. In the future, R&D is going to be very seamless. You converse with AI, and your secure and unstoppable apps or services are created or updated. Cloud engines are designed to directly support this "self-writing cloud" future where we can work hands-free. — Tech sovereignty is becoming a huge issue worldwide, with governments and corporations seeking to create sovereign tech stacks owing to geopolitical tensions. Increasingly, people are realizing that tech provided by foreign nations can come with hidden backdoors and kills switches, from the base platform, right up through hosted apps and services. ICP technology is open source, and those building on ICP using AI own their own source code. When you have the source code, you can verify that there are no backdoors, and when you own the source code thanks to AI, you can update it at will, freeing you from vendor lock-in. But cloud engines take sovereignty much further... — You create a cloud engine by selecting the nodes that will be combined. You can choose the class of nodes used, and their number, but more importantly, you can choose who operates the nodes, and where they are located. Almost any configuration is possible, because the Internet Computer scales the security privileges afforded to hosted software within the network according to configuration (software hosted on cloud engines can directly interoperate with software on other engines and traditional subnets, but base restrictions are applied according to security rules). A cloud engine can be created within a region such as Europe, to comply with regs such as GDPR, or completely within a sovereign state like Switzerland or Pakistan. But cloud engines go further still... — Sovereignty is also about freedom from vendor lock-in. Cloud engines are essentially ICP (Internet Computer Protocol) network configurations, and this means the underlying compute nodes they combine can be swapped out without interrupting their hosted apps and services. This is a big deal. In addition, cloud engines now support nodes that are instances running on Big Tech's clouds, in addition to nodes that are dedicated specialized hardware, as per the Gen I and Gen II nodes that dominate the Internet Computer today. For example, it is possible to have an engine running across different AWS data centers, say, and then reconfigure the engine to run across a mixture of AWS, Google, Azure and Hetzner for even more resilience, without the users of hosted apps and services noticing a thing. That's true freedom. — Sovereign AI is becoming increasingly important too, and cloud engines allow special "AI nodes" to be added to them, so that hosted software can perform inference on hardware provisioned by the owner from a location the owner has selected. Even though the AI nodes are only accessible within the cloud engine, they can still benefit from the forthcoming Internet Intelligence Gateway (IG), which will make it possible to validate inference performed on key frontier open weights LLMs, even when the inference is performed on completely independent AI clouds. When the results of inference are received, this technology can verify that neither the prompt+context (input) nor the inference result (output) have been modified, and that the results were produced by the precise LLM expected. This ensures that AI clouds don't cheat by running inference on cheaper models than are being paid for, and bad actors aren't modifying the inputs or outputs to surreptitiously insert advertising into results, say, or change facts, or insert malware when code is being generated. What's super cool about this technology is the cost of the verification is scalable. A very valuable additional security can be achieved with only 1-2% of extra cost. — Scaling apps and services when they hit capacity limits is another thorny problem that cloud engines help the world address. Engines make scaling possible without rewriting or reconfiguring software. The query workload capacity of hosted software can be horizontally scaled simply by adding new nodes to an engine, and nodes can also be added in geographical proximity to demand. Meanwhile, update workload capacity can first be scaled-up by swapping an engine's nodes out for the next class up, and then when no larger class of node is available, horizontally scaled-out by "splitting" the engine into two, which doubles available capacity. (Technical tip: horizontally scaling update capacity by splitting engines requires multi-canister architectures). — For those who have been following how Caffeine builds apps that can efficiently store large numbers of files, I should mention that apps built on cloud engines will also support the new ICP Blob Storage cloud network (since cloud engines currently have up to about 3 TB of memory, which apps storing large amounts of files can easily exceed). We are also working on allowing blob storage nodes to be added to cloud engines, to enable sovereign mass blob storage within an engine, similarly to how AI nodes can be added currently. — Lastly, but certainly not least, I should mention that cloud engines are multi-blockchain capable, and ready for digital assets, thanks to the clever math at their core. For example, an e-commerce service built on a cloud engine can securely accept and custody stablecoin payments, or a multi-chain DEX could be hosted. Further, engines can support software autonomy (software orchestrated and controlled by other autonomous software, in a decentralized way) and can themselves be orchestrated by SNS technology, and thus run autonomously too. Today, though, the focus is on *mainstream* cloud. This year, the cloud industry will generate approximately one trillion dollars in revenue. That number is already huge, but is expected to grow to two trillion dollars by 2030. After years of continuous development, which have seen more than $500m spent on R&D, the Internet Computer network is now tacking directly toward this mainstream cloud market with cloud engine technology. In their first version, cloud engines are not meant to be a cloud panacea. For example, currently they are not ideal for working with big data. You should use something like DataBricks for that. Cloud engines are carefully targeted at enabling AI to produce traditional online applications and services, including SaaS, in a safer and more productive way, which represents a new market segment with tremendous potential. Of course, DFINITY will continue to work relentlessly to push forward ICP's capabilities, so expect further developments. It's worth mentioning that this cloud segment isn't just about creating new apps and services using AI, it's also about replacing legacy systems and apps built on super expensive SaaS services. Caffeine Labs is working to produce technology (Caffeine Snorkel) that can study an enterprise's legacy systems and app built on SaaS, create replacement systems and apps, and migrate the data, while supporting key stakeholders through the process over email and chat, with full automation. Thus the legacy systems and SaaS markets shall also be addressed by cloud engines. Zooming out, and reasoning in a more metaphysical way, we believe, as we always have, that there is room for a new kind of cloud created by mathematical networks, that provides seminal advances in the fields of security and resilience, as well as true sovereignty and freedom from lock-in. That this same technology, with the help of additional technologies like orthogonal persistence and Motoko, enables AI to build for us without the need for so much oversight, and to create more backend sophistication while consuming fewer AI API tokens, enables ICP to bring game-changing advances to the world. Cloud engines will work synergistically with the Intelligence Gateway, which will enable apps and services running on engines to seamlessly leverage AI, wherever that AI is running, while providing verifiability at extremely low cost for open weights frontier models. We believe that cloud engines represent an inflection point in the storied history of the Internet Computer project, and I'm very proud to be sharing the details with you on the network's fifth birthday 💪 I'll be back with more news soon!!
19:06

Dear ICP community, the Internet Computer has now been running strong for 5 years 👏👏👏 Here is a celebratory preview of ICP "cloud engines," the sovereign frontier cloud technology the network shall soon provide from Main points: — Cloud engines enable anyone to spin up their own sovereign frontier cloud. The technology involves an extraordinary inventive step, in which cloud is created from a mathematically secure network of nodes. The nodes run as part of the Internet Computer network ( but are selected and configured by the cloud engine's owner. — The frontier cloud provided by engines is strongly focused on enabling AI agents to build and update online applications and services for us. The world is changing fast, and nearly all new online apps and services are already being built with the help of AI, and thus cloud engines target the future of cloud. — Software hosted on cloud engines is tamperproof, which means that it is immune to infrastructure hacks, because it runs inside a mathematically secure network protocol, rather than on computers directly. This means that AI agents, and those building with them, don't need to have a security team in the loop, or to trust someone else's security team. This is crucial, because in the future, non technical people will demand the freedom to build with full automation — where they just need to issue instructions to AI about what to build, and don't need to worry about anything or anyone else. Of course, apps and services running on engines are also vastly safer from the new breed of hacker being enabled by frontier AI. (The cloud engines themselves are also "tamperproof." Even if a hacker gains physical access to some portion of a cloud engine's nodes, and can make arbitrary changes, the computations and data of the hosted apps and services cannot be corrupted or interrupted so long as the network's fault bounds aren't exceeded. The recent hack of Vercel, a major cloud platform, which gave hackers access to the apps it hosted, provides additional perspective on the importance of this advantage.) — Software hosted on cloud engines is guaranteed to run, so long as a sufficient number of the engine's nodes are running. This means that AI can build applications and services without the need to have a human systems admin team constantly tinkering with the underlying platform to keep it running, which is again crucial, because in the future, non technical people will expect the freedom to use AI to build without the support of others. — New frontier programming language technology, in the form of the Motoko language developed by Caffeine Labs, leverages seminal "orthogonal persistence" technology that unifies program logic and data to deliver further unlocks for AI (Motoko is the first computer language being developed that targets agents that are writing software rather than humans engineers per se). Nowadays, AI can build and update production apps at a prodigious rate, even at the speed of conversation. But it can also make mistakes, and there's a risk that an update it creates might be "lossy" in the sense it causes some transformed data to be lost. Again, in this new world, it's both undesirable and impractical for everyone to have to have a systems admin team on-hand to detect lossy updates and roll them back, but Motoko provides a solution: it can detect new software updates are lossy before they are applied, reducing potentially catastrophic errors by AI to harmless coding retries. — Software hosted on cloud engines is "serverless" but unlike traditional serverless software, directly it directly incorporates data through "orthogonal persistence." Another key purpose is simplify backend software logic and fuel the modeling power of AI by increasing abstraction (sorry for the technical language!!!). Put simply, this enables AI to produce more sophisticated backends, faster, and at dramatically lower costs, as measured by the number AI API tokens consumed during coding. (Tip for the technical: orthogonal persistence is a new paradigm where "the program is the database," and data lives inside program variables, which is possible because it's as if hosted software runs forever in persistent memory). — An expanding database of skills at shall make it possible to develop and directly deploy apps and services to your cloud engines directly from Claude Code, Perplexity, Codex and other AI platforms. Further, your account on can be connected, so that new apps and updates created through conversation automatically appear hosted from your cloud engine. In the future, R&D is going to be very seamless. You converse with AI, and your secure and unstoppable apps or services are created or updated. Cloud engines are designed to directly support this "self-writing cloud" future where we can work hands-free. — Tech sovereignty is becoming a huge issue worldwide, with governments and corporations seeking to create sovereign tech stacks owing to geopolitical tensions. Increasingly, people are realizing that tech provided by foreign nations can come with hidden backdoors and kills switches, from the base platform, right up through hosted apps and services. ICP technology is open source, and those building on ICP using AI own their own source code. When you have the source code, you can verify that there are no backdoors, and when you own the source code thanks to AI, you can update it at will, freeing you from vendor lock-in. But cloud engines take sovereignty much further... — You create a cloud engine by selecting the nodes that will be combined. You can choose the class of nodes used, and their number, but more importantly, you can choose who operates the nodes, and where they are located. Almost any configuration is possible, because the Internet Computer scales the security privileges afforded to hosted software within the network according to configuration (software hosted on cloud engines can directly interoperate with software on other engines and traditional subnets, but base restrictions are applied according to security rules). A cloud engine can be created within a region such as Europe, to comply with regs such as GDPR, or completely within a sovereign state like Switzerland or Pakistan. But cloud engines go further still... — Sovereignty is also about freedom from vendor lock-in. Cloud engines are essentially ICP (Internet Computer Protocol) network configurations, and this means the underlying compute nodes they combine can be swapped out without interrupting their hosted apps and services. This is a big deal. In addition, cloud engines now support nodes that are instances running on Big Tech's clouds, in addition to nodes that are dedicated specialized hardware, as per the Gen I and Gen II nodes that dominate the Internet Computer today. For example, it is possible to have an engine running across different AWS data centers, say, and then reconfigure the engine to run across a mixture of AWS, Google, Azure and Hetzner for even more resilience, without the users of hosted apps and services noticing a thing. That's true freedom. — Sovereign AI is becoming increasingly important too, and cloud engines allow special "AI nodes" to be added to them, so that hosted software can perform inference on hardware provisioned by the owner from a location the owner has selected. Even though the AI nodes are only accessible within the cloud engine, they can still benefit from the forthcoming Internet Intelligence Gateway (IG), which will make it possible to validate inference performed on key frontier open weights LLMs, even when the inference is performed on completely independent AI clouds. When the results of inference are received, this technology can verify that neither the prompt+context (input) nor the inference result (output) have been modified, and that the results were produced by the precise LLM expected. This ensures that AI clouds don't cheat by running inference on cheaper models than are being paid for, and bad actors aren't modifying the inputs or outputs to surreptitiously insert advertising into results, say, or change facts, or insert malware when code is being generated. What's super cool about this technology is the cost of the verification is scalable. A very valuable additional security can be achieved with only 1-2% of extra cost. — Scaling apps and services when they hit capacity limits is another thorny problem that cloud engines help the world address. Engines make scaling possible without rewriting or reconfiguring software. The query workload capacity of hosted software can be horizontally scaled simply by adding new nodes to an engine, and nodes can also be added in geographical proximity to demand. Meanwhile, update workload capacity can first be scaled-up by swapping an engine's nodes out for the next class up, and then when no larger class of node is available, horizontally scaled-out by "splitting" the engine into two, which doubles available capacity. (Technical tip: horizontally scaling update capacity by splitting engines requires multi-canister architectures). — For those who have been following how Caffeine builds apps that can efficiently store large numbers of files, I should mention that apps built on cloud engines will also support the new ICP Blob Storage cloud network (since cloud engines currently have up to about 3 TB of memory, which apps storing large amounts of files can easily exceed). We are also working on allowing blob storage nodes to be added to cloud engines, to enable sovereign mass blob storage within an engine, similarly to how AI nodes can be added currently. — Lastly, but certainly not least, I should mention that cloud engines are multi-blockchain capable, and ready for digital assets, thanks to the clever math at their core. For example, an e-commerce service built on a cloud engine can securely accept and custody stablecoin payments, or a multi-chain DEX could be hosted. Further, engines can support software autonomy (software orchestrated and controlled by other autonomous software, in a decentralized way) and can themselves be orchestrated by SNS technology, and thus run autonomously too. Today, though, the focus is on *mainstream* cloud. This year, the cloud industry will generate approximately one trillion dollars in revenue. That number is already huge, but is expected to grow to two trillion dollars by 2030. After years of continuous development, which have seen more than $500m spent on R&D, the Internet Computer network is now tacking directly toward this mainstream cloud market with cloud engine technology. In their first version, cloud engines are not meant to be a cloud panacea. For example, currently they are not ideal for working with big data. You should use something like DataBricks for that. Cloud engines are carefully targeted at enabling AI to produce traditional online applications and services, including SaaS, in a safer and more productive way, which represents a new market segment with tremendous potential. Of course, DFINITY will continue to work relentlessly to push forward ICP's capabilities, so expect further developments. It's worth mentioning that this cloud segment isn't just about creating new apps and services using AI, it's also about replacing legacy systems and apps built on super expensive SaaS services. Caffeine Labs is working to produce technology (Caffeine Snorkel) that can study an enterprise's legacy systems and app built on SaaS, create replacement systems and apps, and migrate the data, while supporting key stakeholders through the process over email and chat, with full automation. Thus the legacy systems and SaaS markets shall also be addressed by cloud engines. Zooming out, and reasoning in a more metaphysical way, we believe, as we always have, that there is room for a new kind of cloud created by mathematical networks, that provides seminal advances in the fields of security and resilience, as well as true sovereignty and freedom from lock-in. That this same technology, with the help of additional technologies like orthogonal persistence and Motoko, enables AI to build for us without the need for so much oversight, and to create more backend sophistication while consuming fewer AI API tokens, enables ICP to bring game-changing advances to the world. Cloud engines will work synergistically with the Intelligence Gateway, which will enable apps and services running on engines to seamlessly leverage AI, wherever that AI is running, while providing verifiability at extremely low cost for open weights frontier models. We believe that cloud engines represent an inflection point in the storied history of the Internet Computer project, and I'm very proud to be sharing the details with you on the network's fifth birthday 💪 I'll be back with more news soon!!

dom | icp

300,804 просмотров • 3 месяцев назад

The future of AI Agents needs #ICP AI agents are starting to act on our behalf: - making deals - sending messages - handling sensitive data But there is no trust layer telling you who or what you're actually dealing with ❌ zCloak Network is building exactly that: the trust, identity and privacy infrastructure for the AI-native economy, and they built it on top of Internet Computer Protocol In this podcast I sit down with Xiao Zhang (0xFrancis), founder of to break down what they're building, why they chose ICP over every other blockchain, and what the world looks like when AI agents can finally be trusted.
36:32

The future of AI Agents needs #ICP AI agents are starting to act on our behalf: - making deals - sending messages - handling sensitive data But there is no trust layer telling you who or what you're actually dealing with ❌ zCloak Network is building exactly that: the trust, identity and privacy infrastructure for the AI-native economy, and they built it on top of Internet Computer Protocol In this podcast I sit down with Xiao Zhang (0xFrancis), founder of to break down what they're building, why they chose ICP over every other blockchain, and what the world looks like when AI agents can finally be trusted.

Alex (BCP)

20,791 просмотров • 4 месяцев назад

How is the Web changing due to AI? This visit to TinyFish yesterday goes deeply into just how. TinyFish makes a new kind of web browser. One that is started virtually. It is like a Google Chrome in the cloud. But it is very smart, can read and use any website, and your AI agents can talk to it. Here we talk about what it all means for business and the future of robots, brain computer interfaces, and AI glasses. It lets you build systems that can look at MANY websites at the same time and build new kinds of apps to do all sorts of new things.
1:02:10

How is the Web changing due to AI? This visit to TinyFish yesterday goes deeply into just how. TinyFish makes a new kind of web browser. One that is started virtually. It is like a Google Chrome in the cloud. But it is very smart, can read and use any website, and your AI agents can talk to it. Here we talk about what it all means for business and the future of robots, brain computer interfaces, and AI glasses. It lets you build systems that can look at MANY websites at the same time and build new kinds of apps to do all sorts of new things.

Robert Scoble

16,341 просмотров • 8 месяцев назад

Jensen Huang says agentic AI is not a chatbot. It is a "digital robot" -- and the next bottleneck is not the model. It is first-person data. "Agentic AI is just a digital robot. It understands, it reasons, it plans, and it acts and uses tools." Then he makes the bigger jump: "The world's video data is from a third person, not first person. And so agentic systems, robotic systems, physical AI -- the data is the hardest problem." That is the hidden constraint in robotics. LLMs got the internet. Physical AI needs demonstrations, synthetic worlds, reinforcement learning, and first-person experience. This is why Jensen keeps calling it a stack: robots are not waiting for one magical model. They need the data engine, the simulator, the reward system, the runtime, and the computer. The next wave of AI is not just software that talks. It is software that sees, plans, acts, and eventually moves through the world.
2:32

Jensen Huang says agentic AI is not a chatbot. It is a "digital robot" -- and the next bottleneck is not the model. It is first-person data. "Agentic AI is just a digital robot. It understands, it reasons, it plans, and it acts and uses tools." Then he makes the bigger jump: "The world's video data is from a third person, not first person. And so agentic systems, robotic systems, physical AI -- the data is the hardest problem." That is the hidden constraint in robotics. LLMs got the internet. Physical AI needs demonstrations, synthetic worlds, reinforcement learning, and first-person experience. This is why Jensen keeps calling it a stack: robots are not waiting for one magical model. They need the data engine, the simulator, the reward system, the runtime, and the computer. The next wave of AI is not just software that talks. It is software that sees, plans, acts, and eventually moves through the world.

Karl Mehta

14,140 просмотров • 2 месяцев назад

When we started Score, the standard computer vision tools already existed. About a million people use them every day. Most of those people are still waiting on labels, running training jobs by hand, and watching models fail once they leave the test set. Most of those people are still waiting on labels, running training jobs by hand, and watching models fail once they leave the test set. Most of those people are also still waiting on verified computer vision models, evaluated against real life conditions and ready to be deployed for them to deliver value for their teams, clients or users. Score Studio is the full computer vision path in one place. A team describes the problem. The system can generate the missing scenes, label them, train the candidates, evaluate which ones actually hold, and deploy the winner. Data, labels, training, eval, ship. One loop. If no model exists for that job yet, they can put a bounty on the subnet. Anything from a small vision brick to a full VLM. Miners compete on the task. Only the winning work comes back. Same path for software agents. Any agent can call it. Built to be fully agent-accessible. Built for the people who already do this work: computer vision engineers and the small teams around them in plants, warehouses, farms, robotics, sport, and security. And for the agents those teams will run. That is the part that changes the job. Not another training screen. The stretch that used to take a lab and a calendar, footage, boxes, versions, failed runs, a separate deploy project, sits behind one starting point. And if the network needs a new model, that request is part of the same path. We spent more than a year building it. Then we had a choice. Keep it for us, or commoditize the whole subnet and make it available 24/7, in permissionless and open-source way. And we knew we couldn't keep it for us. It had to live on Bittensor. Open source software already showed how this should work. Infrastructure should not sit inside one company. Same idea as open AI before the phrase changed meaning: inspect it, fork it, keep building. That is what SN44 is for. Open vision intelligence, powered by Bittensor. Miners do the work. Studio is how that gets monetized. Profit does not stay in a company account. It goes back into the subnet through buyback and burn. We built the tool we wanted on day one. It will live on the network now, and for ever. Waitlist is open.
1:11

When we started Score, the standard computer vision tools already existed. About a million people use them every day. Most of those people are still waiting on labels, running training jobs by hand, and watching models fail once they leave the test set. Most of those people are still waiting on labels, running training jobs by hand, and watching models fail once they leave the test set. Most of those people are also still waiting on verified computer vision models, evaluated against real life conditions and ready to be deployed for them to deliver value for their teams, clients or users. Score Studio is the full computer vision path in one place. A team describes the problem. The system can generate the missing scenes, label them, train the candidates, evaluate which ones actually hold, and deploy the winner. Data, labels, training, eval, ship. One loop. If no model exists for that job yet, they can put a bounty on the subnet. Anything from a small vision brick to a full VLM. Miners compete on the task. Only the winning work comes back. Same path for software agents. Any agent can call it. Built to be fully agent-accessible. Built for the people who already do this work: computer vision engineers and the small teams around them in plants, warehouses, farms, robotics, sport, and security. And for the agents those teams will run. That is the part that changes the job. Not another training screen. The stretch that used to take a lab and a calendar, footage, boxes, versions, failed runs, a separate deploy project, sits behind one starting point. And if the network needs a new model, that request is part of the same path. We spent more than a year building it. Then we had a choice. Keep it for us, or commoditize the whole subnet and make it available 24/7, in permissionless and open-source way. And we knew we couldn't keep it for us. It had to live on Bittensor. Open source software already showed how this should work. Infrastructure should not sit inside one company. Same idea as open AI before the phrase changed meaning: inspect it, fork it, keep building. That is what SN44 is for. Open vision intelligence, powered by Bittensor. Miners do the work. Studio is how that gets monetized. Profit does not stay in a company account. It goes back into the subnet through buyback and burn. We built the tool we wanted on day one. It will live on the network now, and for ever. Waitlist is open.

Score

11,075 просмотров • 4 дней назад

SEV Subnets are now live on the Internet Computer. We sat down with Björn Tackmann to understand what they actually are and why they matter. He starts with the problem: standard cloud infrastructure writes your data to memory in plaintext. Anyone with access to the hardware can read it. That's not a flaw in any specific product. It's how computers work. SEV Subnets are the Internet Computer's answer to that. Full conversation below.
1:00

SEV Subnets are now live on the Internet Computer. We sat down with Björn Tackmann to understand what they actually are and why they matter. He starts with the problem: standard cloud infrastructure writes your data to memory in plaintext. Anyone with access to the hardware can read it. That's not a flaw in any specific product. It's how computers work. SEV Subnets are the Internet Computer's answer to that. Full conversation below.

DFINITY Foundation

36,921 просмотров • 2 месяцев назад

A guy named Jan-Christoph accidentally built the most useful directory of open-source projects on the internet. It is called LibreProjects. Search for what you need and it shows you open-source web services across 15 categories: > Social networks > Search engines > Cloud storage > Video calls > Spreadsheets > Presentations > Books > News > Audio > Graphics > Games > Development tools You will find Jitsi Meet for video calls, Nextcloud for cloud storage, EtherCalc for spreadsheets, Searx for search, and Project Gutenberg for books. Click a project and LibreProjects tells you what it does, which commercial product it can replace, what license it uses, and where you can inspect the source code. The clever part is what they refuse to list. A company cannot throw one open-source feature into a paid product and sneak into the directory wearing a fake mustache. The service should be open source, hosted, free to use, and simple enough for ordinary people. It is basically an escape map from subscription software. And somehow, almost nobody knows it exists.
0:38

A guy named Jan-Christoph accidentally built the most useful directory of open-source projects on the internet. It is called LibreProjects. Search for what you need and it shows you open-source web services across 15 categories: > Social networks > Search engines > Cloud storage > Video calls > Spreadsheets > Presentations > Books > News > Audio > Graphics > Games > Development tools You will find Jitsi Meet for video calls, Nextcloud for cloud storage, EtherCalc for spreadsheets, Searx for search, and Project Gutenberg for books. Click a project and LibreProjects tells you what it does, which commercial product it can replace, what license it uses, and where you can inspect the source code. The clever part is what they refuse to list. A company cannot throw one open-source feature into a paid product and sneak into the directory wearing a fake mustache. The service should be open source, hosted, free to use, and simple enough for ordinary people. It is basically an escape map from subscription software. And somehow, almost nobody knows it exists.

Ihtesham Ali

14,089 просмотров • 1 месяц назад

Everyone’s talking about what Jensen said at GTC about AI capex. But the most important thing he said got almost no attention — that software companies are about to become the biggest resellers of AI tokens in the world. Think about what that means. Workday buys raw intelligence from OpenAI. Wraps it in HR domain expertise. Sells it back as an AI product at a massive markup. That’s not a software company anymore. That’s a refinery. And right now nobody is tracking the economics of that refining layer — what the crude costs, what the refined product sells for, and who’s capturing the spread. This is the most important data gap in AI right now. More on this soon. $NVDA
1:06

Everyone’s talking about what Jensen said at GTC about AI capex. But the most important thing he said got almost no attention — that software companies are about to become the biggest resellers of AI tokens in the world. Think about what that means. Workday buys raw intelligence from OpenAI. Wraps it in HR domain expertise. Sells it back as an AI product at a massive markup. That’s not a software company anymore. That’s a refinery. And right now nobody is tracking the economics of that refining layer — what the crude costs, what the refined product sells for, and who’s capturing the spread. This is the most important data gap in AI right now. More on this soon. $NVDA

Nick Dorsey

40,200 просмотров • 5 месяцев назад

"If you're an analytical SaaS company, it's over. It's over." - Palo Alto Networks CEO Nikesh Arora "What is an analytical SaaS company? It is a company that says, “I'm going to collect a lot of data for you and analyze it for you.” I don't need you to analyze it for me. I can run models against the data and analyze it myself. Think about it: almost every SaaS company has a marketplace. You can buy applications from the Salesforce Marketplace. What do those applications say? “You have Salesforce data. I'm a marketplace app. Use me, and I'll help you analyze that data.” But I don't need to do that. You don't need those applications anymore. I can simply run an LLM against the data. Therefore, all the additional functionality that has traditionally been sold to us as incremental software modules may no longer need to be sold separately. I would much rather have an LLM run against the data." ---- From "All-In Podcast" YouTube channel, (full video link in comment)
0:46

"If you're an analytical SaaS company, it's over. It's over." - Palo Alto Networks CEO Nikesh Arora "What is an analytical SaaS company? It is a company that says, “I'm going to collect a lot of data for you and analyze it for you.” I don't need you to analyze it for me. I can run models against the data and analyze it myself. Think about it: almost every SaaS company has a marketplace. You can buy applications from the Salesforce Marketplace. What do those applications say? “You have Salesforce data. I'm a marketplace app. Use me, and I'll help you analyze that data.” But I don't need to do that. You don't need those applications anymore. I can simply run an LLM against the data. Therefore, all the additional functionality that has traditionally been sold to us as incremental software modules may no longer need to be sold separately. I would much rather have an LLM run against the data." ---- From "All-In Podcast" YouTube channel, (full video link in comment)

Rohan Paul

40,959 просмотров • 28 дней назад

Satya Nadella just clarified the Microsoft open Ai deal and the terms what they signed for Azure. Here is exactly how he breaks down the partnership How it was Essentially think of OpenAI having a PaaS business and a SaaS business. The SaaS business is ChatGPT. Their PaaS business is their API. That API is Azure exclusive. The SaaS business, they can run it anywhere. If they want a partner and that partner wants to use a stateless API, then Azure is the place where they can get the stateless API. for even that they'll have to come to Azure. For any custom agreement like that. There are some few exceptions, the US government and so on, that we made, but other than that, they'd have to come to Azure. Open Ai can host there Chat Gpt consumer app wherever they want there wish but when it comes to developers or enterprise want to build on top of Open Ai models Microsoft owned the pipeline.
3:11

Satya Nadella just clarified the Microsoft open Ai deal and the terms what they signed for Azure. Here is exactly how he breaks down the partnership How it was Essentially think of OpenAI having a PaaS business and a SaaS business. The SaaS business is ChatGPT. Their PaaS business is their API. That API is Azure exclusive. The SaaS business, they can run it anywhere. If they want a partner and that partner wants to use a stateless API, then Azure is the place where they can get the stateless API. for even that they'll have to come to Azure. For any custom agreement like that. There are some few exceptions, the US government and so on, that we made, but other than that, they'd have to come to Azure. Open Ai can host there Chat Gpt consumer app wherever they want there wish but when it comes to developers or enterprise want to build on top of Open Ai models Microsoft owned the pipeline.

Vikram M

102,664 просмотров • 29 дней назад

Building with AI gets easier every day. Here is an open-source library that makes integrating AI into an application extremely easy: Star the repository! This library alone can make React the best front-end framework out there! There are a bunch of cool things I like about CopilotKit. Here are 3 of them: 1. It allows you to take any -powered agent and bring it into your application. (This is a brand-new feature!) 2. You can build an AI-powered chatbot in your application. The chatbot will have access to your context and can act on the application. 3. You can build a RAG workflow to process and answer questions from a real-time knowledge base. I recorded a video to show you how simple it is to make some of this happen. A few lines of code, and you are in business. Here is a link to the sample application: CopilotKit is open-source. You can self-host it. You can use it with any LLM. Thanks to the team for showing me their tool and collaborating with me on this post!
5:59

Building with AI gets easier every day. Here is an open-source library that makes integrating AI into an application extremely easy: Star the repository! This library alone can make React the best front-end framework out there! There are a bunch of cool things I like about CopilotKit. Here are 3 of them: 1. It allows you to take any -powered agent and bring it into your application. (This is a brand-new feature!) 2. You can build an AI-powered chatbot in your application. The chatbot will have access to your context and can act on the application. 3. You can build a RAG workflow to process and answer questions from a real-time knowledge base. I recorded a video to show you how simple it is to make some of this happen. A few lines of code, and you are in business. Here is a link to the sample application: CopilotKit is open-source. You can self-host it. You can use it with any LLM. Thanks to the team for showing me their tool and collaborating with me on this post!

Santiago

108,835 просмотров • 2 лет назад

Gokul explains why outcome-based software companies like Zendesk are more exposed to AI than systems of record like NetSuite, and why public markets are not distinguishing between the two. He argues that the only way AI-native startups can disrupt systems of record is by spending 1-2 years building migration tools to get data off of incumbent platforms. "The software companies that should be the most worried right now is where they are pricing the product based on utility. Zendesk is a good example. Instead of paying for 50 Zendesk seats, you can pay for 20 and I can have 30 AI agents sitting next to Zendesk. For these companies you need to change your pricing model to be based on outcome. It's going to be hard for them to stay public. The companies that are less exposed are ones based on data that has been collected and captured over a period of time. ERP is a great example. There is no compelling reason for someone to put their career at stake by ripping out NetSuite. NetSuite has more time to build AI agents on top of it because they have the data, they can train the AI agent on top of it and bundle it. I think the public markets do not distinguish between these two types of companies."
3:06

Gokul explains why outcome-based software companies like Zendesk are more exposed to AI than systems of record like NetSuite, and why public markets are not distinguishing between the two. He argues that the only way AI-native startups can disrupt systems of record is by spending 1-2 years building migration tools to get data off of incumbent platforms. "The software companies that should be the most worried right now is where they are pricing the product based on utility. Zendesk is a good example. Instead of paying for 50 Zendesk seats, you can pay for 20 and I can have 30 AI agents sitting next to Zendesk. For these companies you need to change your pricing model to be based on outcome. It's going to be hard for them to stay public. The companies that are less exposed are ones based on data that has been collected and captured over a period of time. ERP is a great example. There is no compelling reason for someone to put their career at stake by ripping out NetSuite. NetSuite has more time to build AI agents on top of it because they have the data, they can train the AI agent on top of it and bundle it. I think the public markets do not distinguish between these two types of companies."

Patrick OShaughnessy

394,097 просмотров • 7 месяцев назад

Dylan explains why the next wave of private equity looks nothing like the last one. "If we're looking at these companies that are AI rollups, let's take an existing company and completely destroy its cost structure. Nuke its cost structure by just making it efficient with AI." "Private equity companies buy a company, and right now they just squeeze the rag, discard it, and make the American populace screwed." "What new people started to do is the AI private equity strategy. Instead of trying to wring it dry, they're modernizing all the systems. Oh, you use Excel for your databases? Okay, let's move to standard cloud. Spend a lot of money up front." "AI makes that front load much more severe. You spike up on spend a lot for the one time, and then you spike down a lot and your cost efficiency is way better. AI cold calling, AI invoicing, AI accounting, none of it is really at critical mass. But we're so close."
2:42

Dylan explains why the next wave of private equity looks nothing like the last one. "If we're looking at these companies that are AI rollups, let's take an existing company and completely destroy its cost structure. Nuke its cost structure by just making it efficient with AI." "Private equity companies buy a company, and right now they just squeeze the rag, discard it, and make the American populace screwed." "What new people started to do is the AI private equity strategy. Instead of trying to wring it dry, they're modernizing all the systems. Oh, you use Excel for your databases? Okay, let's move to standard cloud. Spend a lot of money up front." "AI makes that front load much more severe. You spike up on spend a lot for the one time, and then you spike down a lot and your cost efficiency is way better. AI cold calling, AI invoicing, AI accounting, none of it is really at critical mass. But we're so close."

SemiAnalysis

72,852 просмотров • 12 дней назад

HERMES JUST GOT A CHATGPT INTERFACE AND IT IS COMPLETELY FREE. No terminal. No command line. No technical setup that takes half a day to figure out. Here is what just became possible. You can now run Hermes, DeepSeek, Ollama, and OpenClaw from a single clean chat interface. Switch between them in one click. Upload files directly. Attach knowledge bases and notes. Preview code without touching the terminal once. Use it on mobile. Make voice and video calls. All of it. Free. Open source. The setup took one conversation with Hermes itself. Pasted the GitHub link in. Hermes installed Open Web UI in Docker on its own. Connected the API server and gateway automatically. A clean ChatGPT-level interface running entirely on local hardware was live in minutes. No subscription. No data leaving your machine. No API bill at the end of the month. The people who set this up this weekend will have a local AI stack that rivals what most companies are paying $2,000 a month for in cloud infrastructure. The people who wait will keep paying for tools that send their data somewhere they cannot see. Both tools are free. Both are open source. The only thing between you and this setup is the next 30 minutes. Follow CyrilXBT for the exact config, setup steps, and local AI workflows I use to run a full stack without spending a dollar on cloud inference.
9:10

HERMES JUST GOT A CHATGPT INTERFACE AND IT IS COMPLETELY FREE. No terminal. No command line. No technical setup that takes half a day to figure out. Here is what just became possible. You can now run Hermes, DeepSeek, Ollama, and OpenClaw from a single clean chat interface. Switch between them in one click. Upload files directly. Attach knowledge bases and notes. Preview code without touching the terminal once. Use it on mobile. Make voice and video calls. All of it. Free. Open source. The setup took one conversation with Hermes itself. Pasted the GitHub link in. Hermes installed Open Web UI in Docker on its own. Connected the API server and gateway automatically. A clean ChatGPT-level interface running entirely on local hardware was live in minutes. No subscription. No data leaving your machine. No API bill at the end of the month. The people who set this up this weekend will have a local AI stack that rivals what most companies are paying $2,000 a month for in cloud infrastructure. The people who wait will keep paying for tools that send their data somewhere they cannot see. Both tools are free. Both are open source. The only thing between you and this setup is the next 30 minutes. Follow CyrilXBT for the exact config, setup steps, and local AI workflows I use to run a full stack without spending a dollar on cloud inference.

CyrilXBT

37,120 просмотров • 4 месяцев назад

99% of AI applications are cool-looking demos. Impressive, but don't get fooled by the hype. It takes a lot to build enterprise-grade products that deliver real value. I have at least three weekly conversations with companies that want to use a Large Language Model with their data. The demand is huge! Here is one idea about what you can do to help. The use cases that most of these companies want to solve are similar: They have an extensive knowledge base and want to build a simple application that uses that information to answer questions. In other words, they need help building Retrieval Augmented Generation (RAG) applications they can use in many different scenarios: 1. To train new employees 2. To help their support team 3. To search old meetings and documents 4. To help with their research However, building these systems is not straightforward. Yes, there's a lot of information online, but there aren't enough people who know how to create solutions that work. Here is the idea: Today, you can build an enterprise-grade RAG application without writing code. A couple of MIT PhDs with 10+ years of experience building AI applications created . It's a no-code platform for building applications using Large Language Models. They are partnering with me on this post. You can use Stack AI to create, test, and deploy an end-to-end production-ready AI system. It's SOC-2, HIPAA, and GDPR compliant and offers SSO, role management, access control, and on-premise deployments. Of course, you can use the platform with any LLM on the market now. It's the whole nine yards for building AI applications. Check them out here: 2023 was about models. 2024 is about the tools using these models to build production-ready applications. That's where I'd start.
0:31

99% of AI applications are cool-looking demos. Impressive, but don't get fooled by the hype. It takes a lot to build enterprise-grade products that deliver real value. I have at least three weekly conversations with companies that want to use a Large Language Model with their data. The demand is huge! Here is one idea about what you can do to help. The use cases that most of these companies want to solve are similar: They have an extensive knowledge base and want to build a simple application that uses that information to answer questions. In other words, they need help building Retrieval Augmented Generation (RAG) applications they can use in many different scenarios: 1. To train new employees 2. To help their support team 3. To search old meetings and documents 4. To help with their research However, building these systems is not straightforward. Yes, there's a lot of information online, but there aren't enough people who know how to create solutions that work. Here is the idea: Today, you can build an enterprise-grade RAG application without writing code. A couple of MIT PhDs with 10+ years of experience building AI applications created . It's a no-code platform for building applications using Large Language Models. They are partnering with me on this post. You can use Stack AI to create, test, and deploy an end-to-end production-ready AI system. It's SOC-2, HIPAA, and GDPR compliant and offers SSO, role management, access control, and on-premise deployments. Of course, you can use the platform with any LLM on the market now. It's the whole nine yards for building AI applications. Check them out here: 2023 was about models. 2024 is about the tools using these models to build production-ready applications. That's where I'd start.

Santiago

197,702 просмотров • 2 лет назад

OpenGradient is the Network for Open Intelligence. We believe that private AI requires: a prompt no operator can read, an identity no one can tie to it, proof in place of trust, and a guarantee that holds even against the people running it — us included.
0:54

OpenGradient is the Network for Open Intelligence. We believe that private AI requires: a prompt no operator can read, an identity no one can tie to it, proof in place of trust, and a guarantee that holds even against the people running it — us included.

OpenGradient (∇, ∇)

1,182,147 просмотров • 3 месяцев назад

the IBM earnings reinforced something I think Wall Street is still underestimating: IBM is becoming an operating system for enterprise AI. The initial earnings reaction focused on the familiar metrics—revenue growth, infrastructure, margins and quarterly expectations. But that misses the bigger transformation underway. The AI market is bifurcating. On one side are companies building frontier models. On the other are companies helping enterprises operationalize AI—integrating it with existing systems and data, governing it, securing it, and turning AI into measurable business outcomes. IBM is increasingly positioning itself for that second market. And that's important because the enterprise AI conversation is moving from models to tools, from experimentation to outcomes, and ultimately toward autonomy and agents. IBM has decades of enterprise infrastructure, software, data and consulting relationships sitting underneath that transition. The mainframe isn't necessarily legacy in this world—it can become part of the context and transaction infrastructure AI acts upon. Wall Street initially looked at the quarter. I think the more important question is what IBM is becoming. My commentary below. #IBM #AI #EnterpriseAI #AgenticAI #HybridCloud
1:31

the IBM earnings reinforced something I think Wall Street is still underestimating: IBM is becoming an operating system for enterprise AI. The initial earnings reaction focused on the familiar metrics—revenue growth, infrastructure, margins and quarterly expectations. But that misses the bigger transformation underway. The AI market is bifurcating. On one side are companies building frontier models. On the other are companies helping enterprises operationalize AI—integrating it with existing systems and data, governing it, securing it, and turning AI into measurable business outcomes. IBM is increasingly positioning itself for that second market. And that's important because the enterprise AI conversation is moving from models to tools, from experimentation to outcomes, and ultimately toward autonomy and agents. IBM has decades of enterprise infrastructure, software, data and consulting relationships sitting underneath that transition. The mainframe isn't necessarily legacy in this world—it can become part of the context and transaction infrastructure AI acts upon. Wall Street initially looked at the quarter. I think the more important question is what IBM is becoming. My commentary below. #IBM #AI #EnterpriseAI #AgenticAI #HybridCloud

John Furrier

47,663 просмотров • 1 месяц назад

Tune Studio is an end-to-end platform for developing applications using Large Language Models. So far, I haven't seen any other platform like this one. You can do everything here: 1. You can curate your data. 2. Use the playground to play with different models and try your ideas. 3. Fine-tune an open-source model on your data. 4. Deploy the model when you are done. This is awesome for anyone building generative AI applications. You can use Tune Studio to work with any of the open-source models out there. They were one of the few companies to host Llama 2 and Llama 3 before anyone else. Here is a link to check it out: One of their main selling points is that Tune Studio scales! You don't have to worry about serving your model to lots of users. They also have built-in user management, authentication, on-prem support, user context management, and pretty much everything you need to build generative AI applications. Thanks to the Tune team for collaborating with me on this post. We are living through the best years of development tools for AI developers. The field is unstoppable.
0:23

Tune Studio is an end-to-end platform for developing applications using Large Language Models. So far, I haven't seen any other platform like this one. You can do everything here: 1. You can curate your data. 2. Use the playground to play with different models and try your ideas. 3. Fine-tune an open-source model on your data. 4. Deploy the model when you are done. This is awesome for anyone building generative AI applications. You can use Tune Studio to work with any of the open-source models out there. They were one of the few companies to host Llama 2 and Llama 3 before anyone else. Here is a link to check it out: One of their main selling points is that Tune Studio scales! You don't have to worry about serving your model to lots of users. They also have built-in user management, authentication, on-prem support, user context management, and pretty much everything you need to build generative AI applications. Thanks to the Tune team for collaborating with me on this post. We are living through the best years of development tools for AI developers. The field is unstoppable.

Santiago

39,101 просмотров • 2 лет назад

ChatGPT connecting to external data sources offers a glimpse into what AI interoperability looks like. Ask any question in ChatGPT and it can now pull data from Box. The future of AI is AI Agents that can access your systems and data to complete any task for you.
0:43

ChatGPT connecting to external data sources offers a glimpse into what AI interoperability looks like. Ask any question in ChatGPT and it can now pull data from Box. The future of AI is AI Agents that can access your systems and data to complete any task for you.

Aaron Levie

57,745 просмотров • 1 год назад

how to use firecrawl to give your AI eyes and actually build startups that outperform 99% of apps: 1. your AI is smart but blind. it can't go to a website, read a page, or grab data on its own. firecrawl fixes that. you put in a URL. you get back clean markdown, structured JSON, screenshots. feed it to any model. 2. three lines of code. that's it. no proxies. no anti-bot detection. no custom scrapers that break when a site changes. one API call. clean data back in seconds. works on 98%+ of sites. 3. firecrawl has six core capabilities: scrape a single page. crawl an entire site. map all URLs on a domain. search google and return full content. an agent endpoint where you describe what you want and it goes and finds it. and a browser sandbox where AI controls a real browser like filling forms, clicking buttons, handles logins. 4. the agent endpoint is wild. you can say "find all of YC's winter 24 dev tool companies and their founders and emails" and get back structured data. or "compare pricing tiers across stripe, square, and paypal" and get a side-by-side table. 5. the browser sandbox lets your AI stay logged in across sessions, navigate pagination, watch live as it browses. this is computer use without building the infrastructure yourself. 6. think of it in layers. every builder needs: an agent harness (claude code, cursor, codex), a search layer (perplexity, exa), a web data layer (firecrawl), an ops brain (obsidian, notion), and an outbound stack. the web data layer is the one most people are sleeping on. 7. this is the AWS moment for web data. in 2006 building a web app meant buying servers and managing racks. AWS said one API call, use our servers. some of the biggest companies of the last decade were built on that. firecrawl is doing the same thing for web data in 2026. 8. the framework i'd use for coming up with startup ideas building with clean data: take a massive horizontal platform. rebuild it for one niche using firecrawl. the vertical version always wins because people want specific, not generic. price for outcome. 9. a year ago firecrawl posted a job listing that said "please only apply if you're an AI agent." content creator agents. customer support agents. junior dev agents. it looked weird. it was a signal for where this is all going. the people who understand how to get clean web data, wrap it around an LLM, and package it as a product are the the ones with a 12-month head start. i use Firecrawl with Idea Browser . once you see what's possible with structured web data, you can't unsee it. episode is live on The Startup Ideas Podcast (SIP) 🧃 (full breakdown there) i tried to explain this as clear as possible for even the non technical. send it to a builder friend. watch
27:27

how to use firecrawl to give your AI eyes and actually build startups that outperform 99% of apps: 1. your AI is smart but blind. it can't go to a website, read a page, or grab data on its own. firecrawl fixes that. you put in a URL. you get back clean markdown, structured JSON, screenshots. feed it to any model. 2. three lines of code. that's it. no proxies. no anti-bot detection. no custom scrapers that break when a site changes. one API call. clean data back in seconds. works on 98%+ of sites. 3. firecrawl has six core capabilities: scrape a single page. crawl an entire site. map all URLs on a domain. search google and return full content. an agent endpoint where you describe what you want and it goes and finds it. and a browser sandbox where AI controls a real browser like filling forms, clicking buttons, handles logins. 4. the agent endpoint is wild. you can say "find all of YC's winter 24 dev tool companies and their founders and emails" and get back structured data. or "compare pricing tiers across stripe, square, and paypal" and get a side-by-side table. 5. the browser sandbox lets your AI stay logged in across sessions, navigate pagination, watch live as it browses. this is computer use without building the infrastructure yourself. 6. think of it in layers. every builder needs: an agent harness (claude code, cursor, codex), a search layer (perplexity, exa), a web data layer (firecrawl), an ops brain (obsidian, notion), and an outbound stack. the web data layer is the one most people are sleeping on. 7. this is the AWS moment for web data. in 2006 building a web app meant buying servers and managing racks. AWS said one API call, use our servers. some of the biggest companies of the last decade were built on that. firecrawl is doing the same thing for web data in 2026. 8. the framework i'd use for coming up with startup ideas building with clean data: take a massive horizontal platform. rebuild it for one niche using firecrawl. the vertical version always wins because people want specific, not generic. price for outcome. 9. a year ago firecrawl posted a job listing that said "please only apply if you're an AI agent." content creator agents. customer support agents. junior dev agents. it looked weird. it was a signal for where this is all going. the people who understand how to get clean web data, wrap it around an LLM, and package it as a product are the the ones with a 12-month head start. i use Firecrawl with Idea Browser . once you see what's possible with structured web data, you can't unsee it. episode is live on The Startup Ideas Podcast (SIP) 🧃 (full breakdown there) i tried to explain this as clear as possible for even the non technical. send it to a builder friend. watch

GREG ISENBERG

135,254 просмотров • 5 месяцев назад