Infrasity wrote 193 posts for DotFiles Insider, Daytona's developer blog, built its SDK examples repo, and tracked every post on Google and in AI answers. In that time, Daytona pivoted 3 times, from dev environments to AI agent sandboxes, reached #1 Product of the Day on Product Hunt, and raised a $60M Series B at a $1B valuation in October 2026. Google AI Overviews now cite Daytona blog posts in 62 answers, and the Series A announcement Infrasity wrote ranks #1 on Google for "daytona funding".
TL;DR
- Infrasity wrote 193 DotFiles Insider posts and moved the blog's topics with each of Daytona's pivots, from dev environments to AI agent sandboxes.
- Infrasity built the sdk-examples repo with 4 runnable AI use cases on the Daytona SDK, shipped in the months before the April 2025 relaunch that reached #1 on Product Hunt.
- Google AI Overviews cite 27 Daytona blog posts across 62 answers, and the staging and production explainer alone appears in 23.
- Blog posts rank #1 on Google for "daytona funding" and "daytona windows", and Google's AI Overview for "open swe" names Daytona and cites the post Infrasity wrote.
- Infrasity founder Shantanu Das hosted Daytona founder Ivan Burazin on the Infrasity podcast in October 2024 to talk about developer marketing, go-to-market experiments and fundraising.
What did the Daytona program deliver?
The program shipped a blog, an example repo and a tracking system, and each one left measurable proof on Google and in AI answers.
| Result | Detail |
|---|---|
| 193 blog posts | DotFiles Insider posts across 5 topic clusters, from dev environments to AI agent sandboxes |
| 62 AI Overview answers | Google AI Overview answers that cite a Daytona blog post, with 27 posts cited in total |
| 23 answers for one post | Understanding Development, Staging, and Production, the most cited page on daytona.io |
| 20 top-10 rankings | Blog keywords in Google's top 10, 3 of them at #1 |
| 4 SDK use cases | Claude, SmolAgents, OpenAI Evals and PydanticAI examples running in Daytona sandboxes |
| 7.4x site-wide ranking keywords | daytona.io went from 305 (Apr 2024) to 2,242 (Mar 2026) ranking keywords while the blog ran |
What does Daytona do, and where did Infrasity help?
Daytona gives AI agents secure, isolated sandboxes to run the code they generate. Developers create a sandbox with one SDK call, run code inside it, and delete it when done. The SDK ships for Python, TypeScript, Ruby, Go, and Java.
Daytona's buyers are engineers building coding agents, evaluation pipelines and agent platforms. They judge a tool by working examples and clear explanations before they talk to anyone, so the content had to be accurate enough to copy and run.
| Client | Category | Where Infrasity helped | Window |
|---|---|---|---|
| Daytona | Secure infrastructure for AI-generated code | DotFiles Insider blog, SDK examples repo, search and AI visibility tracking | About 18 months |
Daytona's homepage shows the whole product in one block of code: create a sandbox, run code, delete it.
The company grew fast in the same period. Daytona went from $1M to $100M run rate in four quarters, raised a $24M Series A in February 2026 and a $60M Series B in October 2026, bringing total funding to $91M. Each of those moments reached developers through a DotFiles Insider post, and the Series A post still ranks #1 on Google for "daytona funding".
What did Daytona's founder share about developer marketing on the Infrasity podcast?
In October 2024, Infrasity founder Shantanu Das hosted Daytona co-founder and CEO Ivan Burazin on the Infrasity YouTube channel. The 45-minute episode has 6.6K views, and it records Daytona at its dev environment stage, before the move to AI sandboxes.
The episode page describes Daytona as it was then: a self-hosted, open source development environment manager.
The episode ran two years before the agent cloud pivot, when Daytona was still a development environment manager.
The parts that shaped how Infrasity ran Daytona's content:
- Developers were the buyer from day one. Ivan's earlier companies were Codeanywhere, a browser-based code editor started in 2009 with about 2.5 million users, and Shift, a developer conference later acquired by Infobip.
- Go-to-market runs as small experiments. Daytona tried content, online communities, meetups and conferences on small budgets, kept what worked twice and dropped the rest.
- Fundraising starts with self-awareness. Ivan raised Daytona's first $2M from about 60 angels and advised founders to pitch global investors and keep cold emailing.
- Early hires should already know you. He said he would fill the first 10 to 15 roles with people he had worked with before.
Watch the full conversation on Infrasity's YouTube channel.
Where did Daytona stand before Infrasity started?
Daytona had a strong open-source following, little search presence, and a product that kept changing category. Three problems shaped the program.
Search visibility was thin
In April 2024, daytona.io ranked for 305 keywords on Google US. Only 26 were in the top 10, none at #1, and the site drew an estimated 228 organic visits a month.
Daytona pivoted 3 times in under 3 years
Daytona started out selling dev boxes: automated, on-prem development environments for large engineering teams. In March 2024 it went open source as a development environment manager, and by the end of 2024 the repo had 13,826 GitHub stars. In February 2025 the team sunset that product and let go of its customers, then relaunched in April 2025 as infrastructure for running AI-generated code. With the October 2026 Series B, it now calls itself an agent cloud.
Every pivot brought a new buyer and a new set of searches, so the blog had to change with the product each time.
Three pivots in under three years, with the two moments Infrasity was part of marked in blue.
Developers needed proof before they would try it
Agent builders compare sandboxes like E2B, Modal and Vercel Sandbox side by side. A sandbox they cannot test in five minutes gets dropped, so Daytona needed runnable examples and plain explanations next to its product pages.
How did Infrasity build Daytona's content system?
Infrasity ran 3 workstreams that fed each other: the blog explained every change, the example repo proved the SDK worked, and tracking showed what to write next.
Each workstream fed the next: the blog explained the product, the repo proved it, and tracking decided what came after.
Publishing every launch and explainer on DotFiles Insider
Infrasity wrote 193 posts for DotFiles Insider, Daytona's weekly blog for developers. The plan grouped posts into five clusters, so each one had a job.
- Developer experience and dev environments: 95 posts
- AI sandboxes and agent runtimes: 57 posts
- Open source and community: 16 posts
- Product launches and features: 13 posts
- Funding, company news and events: 12 posts
The topic mix followed the product. Dev environment posts made up most of 2023 and 2024, and from the first half of 2025 AI sandbox posts took over.
The topic mix flipped from dev environments to AI sandboxes in the same half year as the April 2025 relaunch.
DotFiles Insider today, with the latest company updates at the top of the index.
The blog index carries launches, funding news and explainers in one weekly feed.
Every post sits in the blog plan with its cluster, URL, top ranking keyword, Google position and whether Google's AI Overview cites it.
Every post is tracked by cluster, keyword, Google position and AI Overview citation status.
Want a blog that keeps up with your product? Book a call about technical content marketing.
Writing the launch week posts for the April 2025 relaunch
Daytona relaunched as AI sandbox infrastructure in the last week of April 2025 with a launch week. Infrasity wrote the posts that carried it: Introducing Daytona Cloud, the Web Terminal, new regions, the MCP server and the launch week recap. Daytona was named #1 Product of the Day on Product Hunt on April 30 and #1 SaaS product of the month.
Daytona's newsletter to its community on 2 May 2025 shared both results.
The newsletter went out two days after launch week closed, with both Product Hunt placements confirmed.
About 2 months after the relaunch, Daytona crossed $1M in annual recurring revenue.
Building runnable SDK examples for four AI frameworks
In early 2025, right as Daytona moved to AI sandboxes, Infrasity built the sdk-examples repo. Infrasity engineers wrote about 37 of its 41 commits between January and March 2025.
- claude-code-interpreter: Claude and MCP run Python inside an isolated Daytona sandbox.
- smolagents-code-tester: a Hugging Face SmolAgents agent writes tests and runs them in a sandbox.
- openai-evals-ai-evaluator: several versions of a function run in separate sandboxes and the best one wins.
- ai-github-summarizer: clones any repo into a sandbox and writes a structured summary with PydanticAI.
The repo on GitHub, with its four use case folders.
Four runnable use cases, each one a folder a developer can clone and run.
The examples were logged in the same plan so blog posts could link back to them.
Each example was tracked alongside the posts, so the blog could link to working code.
Want example repos that show your SDK working? See Infrasity's GitHub marketing service or book a call.
Tracking rankings and AI citations for every page
Infrasity mapped each blog post to the keyword it ranks for and checked whether Google's AI Overview cites it. That list shows which topics earn traffic and which ones to write next.
Twenty blog keywords sit in Google's top 10, with "daytona funding" and "open swe" marked.
Developers now meet a product through AI agents as often as through search, and those agents read pages through crawlers before they answer. Infrasity runs this tracking inside its Content Hub, where the Dev Intelligence feature shows which AI agents and bots crawl a site's pages, which pages they cite most, and which pages need fixing.
Want to know which of your pages AI engines cite? Get a free AEO audit or explore AEO and GEO services.
What results did Daytona get on Google and in AI answers?
The rankings and citations below come from DataForSEO, pulled on 10 November 2026 for Google US.
daytona.io's ranking keywords grew 7.4x while the blog ran
From April 2024 to the March 2026 peak, daytona.io went from 305 to 2,242 ranking keywords. Estimated organic visits peaked at 4,873 a month in April 2026, up from 228. Keywords in the top 10 grew from 26 to 106, and #1 rankings went from none to 11. These are site-wide figures, and blog posts are one part of them.
Ranking keywords grew 7.4x and estimated organic visits grew more than 21x over the two years the blog ran.
Blog posts hold #1 on Google for Daytona's funding and Windows searches
The Series A post ranks #1 for "daytona funding", the Windows sandboxes post ranks #1 for "daytona windows", and a post on the holy triangle of software development ranks #1 for "quality of software development". In all, 20 blog keywords sit in Google's top 10.
Google's AI Overview names Daytona and cites the blog for "open swe"
The post LangChain's Open SWE Runs on Daytona ranks on page one for "open swe" (260 searches a month). Google's AI Overview for the same search says Open SWE runs code in cloud sandboxes such as Daytona, and cites that post.
The answer names Daytona in the line about isolated cloud sandboxes, with Daytona attached as a source.
The Daytona post also appears as a source card under the same AI Overview.
The post Infrasity wrote sits in the source carousel next to LangChain's own page.
Google AI Overviews cite 27 blog posts in 62 answers
We found that daytona.io is cited in 173 Google AI Overview answers, and 62 of them cite a blog post. The most cited page on the whole site is the blog post Understanding Development, Staging, and Production, used in 23 answers for searches like "staging vs production" and "what is a staging environment".
One explainer accounts for 23 of the 62 AI Overview answers that cite a Daytona blog post.
ChatGPT ranks Daytona first among E2B alternatives
Asked "What are the best alternatives to E2B for AI agent sandboxes?", ChatGPT lists Daytona first and labels it the best overall alternative. In five buying prompts run through the ChatGPT scraper, Daytona was named in four.
Daytona heads both the comparison table and the ranked list, tagged as the best overall alternative.
Want your product named in AI answers for your category? Book a call or start with a free AEO audit.
What can other DevTool teams learn from the Daytona program?
Five lessons came out of the Daytona program. Each one can be applied to any developer product.
Move the blog when the product moves
Daytona's blog went from mostly dev environment posts in 2024 to mostly AI sandbox posts in 2025, in the same half year as the relaunch. A blog that keeps writing for the old buyer after a pivot sends traffic to a product that no longer exists.
Give every launch and funding round its own post
Launches like volumes, Dockerfile support, the declarative image builder and Windows sandboxes each got their own post. The Windows post now ranks #1 for "daytona windows", and the Series A post ranks #1 for "daytona funding". Regular posts also gave Daytona's community a steady source of updates between releases.
Evergreen explainers keep getting cited
The staging and production explainer is the single most cited daytona.io page in Google AI Overviews, used in 23 answers. A clear definition of a basic concept keeps earning citations long after the post goes live.
Example repos need distribution to earn stars
The sdk-examples repo proved the SDK works with four frameworks, yet it has 7 stars. Code sitting in a repo gets little traffic, so every example needs a blog post, links from the product pages and a launch plan that points people to it.
Run go-to-market as small experiments
Ivan Burazin told the Infrasity podcast that Daytona tests each channel on a small budget and only doubles down when it works twice. Content programs benefit from the same rule: track every post, keep the topics that rank and get cited, and drop the rest.
Want this system built for your product? Book a free consultation with Infrasity's developer marketing team.
What would Infrasity do differently on the Daytona program?
Two gaps stand out in the data, and both shape how Infrasity runs DevTool programs today.
- Category comparison pages, earlier. daytona.io does not rank in the top 10 for "e2b alternative", "ai agent sandbox" or "ai code sandbox". Third-party roundups rank there and name Daytona, so owned alternative and comparison pages would have captured that demand directly.
- A launch plan for every example repo. The four SDK examples were solid code with little reach. Listing them in awesome lists, linking them from each related blog post and the product pages, and posting them in developer communities would have turned them into a steady source of stars and signups.
How would you run this program for your own developer product?
- List the launches, features and integrations on your roadmap, and plan one post for each.
- Write evergreen explainers for the basic concepts your buyers search for.
- Build two to four runnable example repos and link each one from a matching post.
- When the product changes direction, move the blog's topics with it in the same quarter.
- Track every post against its ranking keyword and whether Google AI Overviews or ChatGPT cite it, and watch which AI crawlers read your pages.
- Use that tracker each month to pick the next posts, starting with comparison and alternative searches you do not yet rank for.
Which Infrasity services supported Daytona, and what did each one drive?
| Service | What Daytona got | The result it drove |
|---|---|---|
| Technical content marketing | 193 DotFiles Insider posts across five clusters, including the April 2025 launch week | 62 Google AI Overview answers citing 27 posts, #1 for "daytona funding" and "daytona windows" |
| GitHub marketing | The sdk-examples repo with four AI framework use cases | Runnable proof of the SDK during the April 2025 relaunch |
| AEO and GEO | Page-level tracking of rankings and AI citations, with AI crawler tracking in Dev Intelligence | The most cited page on daytona.io in AI Overviews is a blog post, used in 23 answers |
Want content that keeps pace with your developer product?
Infrasity writes blog content, example repos and launch posts for DevTool and AI infrastructure teams, then tracks every page on Google and in AI answers. Book a call, get a free AEO audit, or read more case studies.
Frequently Asked Questions
How often should an early developer tool publish blog posts?
Daytona's blog is published about weekly, with a post for every launch and evergreen explainers in between. A steady cadence keeps the community current and gives search engines and AI assistants new pages to cite.
How should a developer tool change its content after a pivot?
Move the topic mix in the same quarter as the product. Daytona's blog switched from dev environment posts to AI sandbox posts in the half-year of its April 2025 relaunch, and the launch week posts introduced the new product to existing readers.
How does content get cited in Google AI Overviews?
Pages that answer one question plainly get cited most. Daytona's most cited page is a basic explainer on development, staging and production environments, used in 23 AI Overview answers.
How do you track AI crawler visits and AI citations for your content?
Infrasity maps every page to the searches and buying prompts it should win, then checks rankings on Google and citations in AI Overviews and ChatGPT each month. Dev Intelligence in Infrasity's Content Hub adds which AI agents and bots crawl each page. Teams can start with a free AEO audit.
How do example repos earn GitHub stars after launch?
Stars follow distribution. Link each example from a matching blog post and the product pages, list it in awesome lists and share it in developer communities in the launch month.
