-
Notifications
You must be signed in to change notification settings - Fork 6
aug update #282
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
Merged
aug update #282
Changes from 6 commits
Commits
Show all changes
8 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 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 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](https://docs.defang.io/docs/tutorials/deploy-to-aws) and [GCP](https://docs.defang.io/docs/tutorials/deploy-to-gcp) through the [Defang MCP Server](https://docs.defang.io/docs/concepts/mcp) 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. |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe add a "legacy" - "As more and more teams are moving away from legacy PaaS solutions..."