-
Notifications
You must be signed in to change notification settings - Fork 6
agentic era blog #288
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+67
−0
Merged
agentic era blog #288
Changes from 9 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
7d9d325
Add Agentic Apps blog post with hero image
tokifyi 443e7c5
Update blog: DO -> DigitalOcean wording
tokifyi ae48a27
Agentic Apps: add Agentic Strands sample link
tokifyi 4ddd8f1
Merge branch 'main' into main
tokifyi f3fc767
Merge branch 'DefangLabs:main' into main
tokifyi 770f105
August monthly update
tokifyi cc1cfd9
August monthly update (legacy)
tokifyi 356c90b
August update: updated the MCP link
tokifyi 2a635f2
Add Agentic Era blog post with image - September 15, 2025
tokifyi 4a77a2b
Update Agentic Era blog post content
tokifyi d751be8
Remove August product updates blog post
tokifyi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,52 @@ | ||
--- | ||
title: "August 2025 Defang Compose Update" | ||
description: "Monthly product updates from the Defang team - August 2025" | ||
slug: 2025-09-09-product-update | ||
tags: | ||
[ | ||
Cloud, | ||
NoDevOps, | ||
BYOC, | ||
GCP, | ||
AWS, | ||
AI, | ||
LLMs, | ||
Railpack, | ||
Cost Estimation, | ||
Agentic Apps, | ||
Defang Compose Update, | ||
] | ||
author: Defang Team | ||
--- | ||
|
||
 | ||
|
||
August was about making migrations smoother and showing how you can already use Defang to deploy agentic apps at scale. We expanded our sample projects for popular multi-agent frameworks like CrewAI, LangGraph, Autogen, and Strands, validating them on Playground, AWS, and GCP so you can run multi-agent workloads in production without extra DevOps. Our new Heroku migration flow inspects dynos and add-ons, generates a clean Compose file, provisions managed equivalents like Postgres and Redis, and ships to your own cloud in one command. This cuts costs and removes lock-in. We also introduced MCP BYOC prompts so you can deploy to AWS and GCP straight from your IDE. Railpack on GCP now delivers faster, more reliable no-Dockerfile builds with clearer logs and closer parity with AWS. | ||
|
||
## Heroku Migration | ||
|
||
As more and more teams are moving away from legacy PaaS solutions, looking for more flexibility and more control, we’ve made it easier for teams to move off [Heroku](https://docs.defang.io/docs/tutorials/migrating-from-heroku). Defang now supports deployments without a Dockerfile and Defang will even generate a compose file from your Heroku application. The result is a smoother path to AWS or GCP with more features, lower costs, and no lock-in. | ||
|
||
## Agentic Applications | ||
|
||
We expanded and refined our sample projects for agentic frameworks like CrewAI, LangGraph, Autogen, and Strands, validating across Playground, AWS, and GCP for a seamless move to production. [Agentic applications](https://docs.defang.io/blog/agentic-apps) demand more than code. They need scalable compute, managed databases and caches, security, orchestration, and LLM integrations. That’s why Defang automates all the heavy lifting. When you define your app once in Docker Compose, Defang handles provisioning on AWS or GCP including compute, managed Postgres or MongoDB, Redis, LLM services, security, auto scaling, and compliance so you can focus purely on your agents. | ||
|
||
## MCP BYOC Prompts | ||
|
||
We now support deploying to AWS and GCP through the [Defang MCP Server](http://docs.defang.io/docs/tutorials/deploying-with-the-defang-mcp-server) using prompts in your IDE. This keeps your workflow fast and frictionless, letting you go from code to cloud in seconds without breaking focus. You can stay in the flow with no context switching, spinning up services or scaling workloads simply by chatting in your editor. It means faster iteration, shorter feedback loops, and less time wrestling with terminals or cloud consoles. | ||
|
||
:::note | ||
Requires Defang CLI v2.1.3 or later. | ||
::: | ||
|
||
## Railpack GCP | ||
|
||
[Railpack](https://docs.defang.io/docs/concepts/railpack) now works more smoothly on GCP with fixes to image builds, provider consistency, and a redesigned repo. You’ll see faster first builds and rebuilds with better caching, clearer logs when something fails, and closer parity with AWS so templates behave the same across clouds. Railpack also auto-detects common stacks when no Dockerfile is present, applies sensible defaults for runtime, ports, and health checks, and produces clean OCI images for Playground or your own cloud. Net result: you can ship no-Dockerfile apps across clouds with less setup and fewer surprises. | ||
|
||
## Events and Community | ||
|
||
In August, one of our campus advocates, Swapnendu Banerjee, hosted a [session](https://www.linkedin.com/posts/rajanyamaity_statuscode2-iiitkalyani-iiserkolkata-activity-7365717326035374081-Ky-S/) that showed how quickly you can deploy real apps to the cloud with Defang. Looking ahead, we’ll be at the [ALL IN conference](https://allinevent.ai/) in Montreal this month and would love to connect if you’re a Defang user or planning to attend. | ||
|
||
We are excited to see what you will deploy with Defang next. Join our [Discord](https://s.defang.io/discord) to ask questions, get support, and share your builds with the community. | ||
|
||
More coming in September. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,67 @@ | ||
--- | ||
title: "Deployments in the Agentic Era" | ||
description: "How agentic applications are reshaping the future of software development and deployment" | ||
slug: agentic-era | ||
tags: [Agentic Era, AI, Software Development, Future, Automation, Cloud, DevOps] | ||
author: Defang Team | ||
date: 2025-09-15 | ||
--- | ||
|
||
# **Deployments in the Agentic Era** | ||
|
||
If you want people to adopt your AI product, the deployment story has to be as strong as the features. | ||
|
||
Over the past few decades, the software industry has gone through 3 major eras. Each one reshaped not only how products are delivered, but also how they are trusted. | ||
tokifyi marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
- In the **Client-Server Era** (circa 2000)**,** apps like SAP and PeopleSoft were purchased and deployed by the customer in their own "on-prem" environment. The customer was in control, but also took on the operational complexity of everything from procuring and deploying hardware to the system software and the apps themselves. | ||
- In the **SaaS Era** (circa 2010s), apps such as Salesforce and Workday ran in the provider's cloud and were delivered through the browser. While this simplified operations for the customer, it also meant that the customer data was trapped in these applications, with sometimes ambiguous data ownership and usage rules. | ||
- Today, we are entering the **Agentic Era**. Agentic apps promise to deliver an unprecedented productivity boost, but to do so, they need access to the most sensitive business data: conversations, documents, decisions. Customers do not want to transfer such data to an unknown and untrusted external provider's environment. Instead, they expect these products to run inside _their_ cloud accounts (whether it be [AWS](https://aws.amazon.com/), [GCP](https://cloud.google.com/), or any other), with _their_ compliance, and under _their_ security controls. | ||
|
||
 | ||
|
||
This is not a small adjustment. It is the foundation of how the next generation of software will be trusted and adopted. | ||
|
||
## **Why the Agentic Era Changes the Rules** | ||
|
||
AI products are not like SaaS tools. They do not just manage workflows, they ingest and act on the crown jewels of a business. To succeed in this environment, three conditions must hold true: | ||
|
||
- **Data stays with the customer**: no leaking sensitive content outside their environment. | ||
- **Deployments work across clouds**: [AWS](https://aws.amazon.com/), [GCP](https://cloud.google.com/), [Azure](https://azure.microsoft.com/en-us/), or wherever the customer operates. | ||
- **Security and compliance are built in**: IAM, networking, and policies set up correctly from day one. | ||
|
||
This is not a technical detail. It is the trust layer that determines whether adoption happens at all. | ||
|
||
## **ekai's Example** | ||
|
||
[ekai](https://yourekai.com/) is an AI digital twin that boosts productivity by capturing meetings, surfacing action items, and acting as a Slack companion. To be trusted, it has to run inside the customer's cloud account. | ||
|
||
ekai needed a single deployment solution that could run on any cloud and deliver a consistent, reliable experience with the same features everywhere. Like many AI builders, they faced the challenge of providing secure, compliant deployments across [AWS](https://aws.amazon.com/), [GCP](https://cloud.google.com/), and other environments without spending weeks on custom DevOps for each customer. | ||
|
||
That is where Defang came in. | ||
|
||
With Defang, ekai defines its application once in Docker Compose. Defang turns that definition into a production-ready deployment inside the customer's own cloud account. Compute, storage, networking, IAM roles, security groups, and even managed LLMs are provisioned automatically, following best practices for each cloud. | ||
|
||
What used to take weeks of engineering now happens in hours. More importantly, every deployment is secure, compliant, and customer-owned. | ||
|
||
> "Defang was the ideal choice for us. We simply describe ekai as a Docker Compose application, and Defang takes care of everything else. From compute and storage to IAM roles and managed LLMs, Defang ensures our deployments are secure, scalable, and cloud-native. That is a huge benefit for us and for our customers." | ||
|
||
**Ash Tiwari, Founder & CEO, [ekai](https://yourekai.com/)** | ||
|
||
## **Defang and the Agentic Era** | ||
|
||
ekai is not an isolated case. It is a preview of what the Agentic Era demands. As AI products move deeper into mission-critical workflows, deployment will decide adoption. | ||
|
||
Defang exists to make this possible. | ||
|
||
- Define your app once, no matter the framework: [CrewAI](https://www.crewai.com/), [LangGraph](https://www.langchain.com/langgraph), [AutoGen](https://microsoft.github.io/autogen/stable//index.html), [Strands](https://strandsagents.com/latest/) | ||
- Deploy to any cloud in a single step | ||
- Keep customer data inside customer environments | ||
- Align deployments with cloud-native best practices automatically | ||
|
||
Just as SaaS platforms unlocked a decade of cloud adoption, Defang is the foundation for customer-owned AI. | ||
|
||
## **The Takeaway** | ||
|
||
In the Agentic Era, trust is the product. The next wave of AI adoption will be decided not by features, but by where and how products run. Companies that respect data ownership and deliver secure, cloud-native deployments will earn trust and scale. Those that do not will be left behind. | ||
|
||
Defang is the invisible infrastructure making this era possible. |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.