From a29daf59e3168785b4cca65b7ed64d29c9665074 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Rapha=C3=ABl=20Titsworth-Morin?= Date: Mon, 13 Apr 2026 16:30:48 +0000 Subject: [PATCH 1/2] docs: remove all Defang Playground references The Defang Playground is being removed. This commit: - Deletes dedicated Playground pages (defang-playground.md, deploy-to-playground.mdx, providers/playground.md) - Removes Playground rows from all provider support tables - Updates domain examples from defang.dev to defang.app format - Removes Playground/BYOC tabs where Playground was the only alternative - Updates blog posts to remove forward-looking Playground references - Fixes broken links to deleted pages - Updates getting-started, FAQ, and intro pages Closes #360 Co-Authored-By: Claude Opus 4.6 --- ...024-02-12-announcing-defang-public-beta.md | 2 +- blog/2024-06-01-june-product-updates.md | 6 +- blog/2024-07-01-july-product-updates.md | 2 +- blog/2024-07-31-july-product-updates-2.md | 2 +- blog/2024-08-30-august-product-updates.md | 2 +- blog/2024-09-30-september-product-updates.md | 4 +- blog/2024-11-13-october-product-updates.md | 2 +- blog/2025-02-07-january-product-updates.md | 2 +- ...2025-04-10-easiest-way-to-deploy-django.md | 4 +- blog/2025-04-23-vibe-deploy.md | 4 +- blog/2025-06-06-may-product-updates.md | 10 ++- blog/2025-06-16-crew-ai-sample.md | 6 +- blog/2025-07-10-june-product-updates.md | 6 +- blog/2025-08-07-defang-ai-devops-agent.md | 2 +- blog/2025-08-22-agentic-apps.md | 3 +- blog/2025-09-09-august-product-updates.md | 6 +- blog/2025-10-17-september-product-updates.md | 2 +- docs/concepts/accounts.md | 4 +- docs/concepts/configuration.md | 1 - docs/concepts/defang-byoc.md | 5 +- docs/concepts/defang-playground.md | 30 -------- docs/concepts/deployments.md | 4 +- docs/concepts/domains.mdx | 20 ++---- docs/concepts/estimation.md | 1 - .../managed-llms/managed-language-models.md | 4 -- .../managed-llms/openai-access-gateway.md | 1 - .../managed-storage/managed-mongodb.md | 1 - .../managed-storage/managed-object-storage.md | 1 - .../managed-storage/managed-postgres.mdx | 1 - .../concepts/managed-storage/managed-redis.md | 1 - docs/concepts/networking.mdx | 19 +---- docs/concepts/observability.md | 3 - docs/concepts/one-off-jobs.md | 1 - docs/concepts/portal.md | 7 +- docs/concepts/pulumi.md | 2 +- docs/concepts/railpack.md | 1 - docs/concepts/scaling.md | 1 - docs/concepts/services.md | 21 ++---- docs/intro/faq/questions.md | 6 +- docs/intro/getting-started.mdx | 4 +- docs/intro/intro.mdx | 10 +-- docs/intro/what-is-defang.mdx | 3 +- docs/providers/playground.md | 25 ------- .../adding-custom-one-click-deploy.md | 4 +- docs/tutorials/deploy-to-playground.mdx | 69 ------------------- docs/tutorials/deploy-to-your-cloud.mdx | 1 - docs/tutorials/deploy-using-pulumi.mdx | 4 +- docs/tutorials/deploy-with-gpu.mdx | 2 +- .../deploying-with-the-defang-mcp-server.md | 18 +---- docs/tutorials/migrating-from-heroku.md | 2 +- docs/tutorials/monitoring-your-services.md | 9 +-- docs/tutorials/using-one-click-deploy.md | 12 ++-- src/pages/index.tsx | 9 +-- 53 files changed, 73 insertions(+), 299 deletions(-) delete mode 100644 docs/concepts/defang-playground.md delete mode 100644 docs/providers/playground.md delete mode 100644 docs/tutorials/deploy-to-playground.mdx diff --git a/blog/2024-02-12-announcing-defang-public-beta.md b/blog/2024-02-12-announcing-defang-public-beta.md index aa32230c52..09c7b76847 100644 --- a/blog/2024-02-12-announcing-defang-public-beta.md +++ b/blog/2024-02-12-announcing-defang-public-beta.md @@ -9,7 +9,7 @@ tags: [Cloud, GenerativeAI, NoDevOps, BYOC, AWS] Ever since we shipped our Private Beta in the summer of 2023, we have been working with early adopters and listening to their feedback. While these early customers loved the ease with which they could create, deploy, and manage a cloud application, they had one big request - to deploy their applications to their own cloud (e.g. AWS) account. This was important to them for a number of reasons - to leverage their cloud credits, to enforce their IAM roles and security settings, to integrate new application components with their existing deployments, and more. -And so, today with our Public Beta, we are addressing this request. With today’s release of [Defang BYOC](/docs/concepts/defang-byoc) (Bring-your-own-Cloud), you can now enjoy all the benefits of Defang **and** deploy applications to your own AWS account! Our Private Beta experience is still available as [Defang Playground](/docs/concepts/defang-playground) for you to quickly and easily prototype applications and deploy them to our hosted environment. +And so, today with our Public Beta, we are addressing this request. With today’s release of [Defang BYOC](/docs/concepts/defang-byoc) (Bring-your-own-Cloud), you can now enjoy all the benefits of Defang **and** deploy applications to your own AWS account! You can learn more about Defang [here](/docs/intro). Also check out our [tutorials](/docs/tutorials), [samples](https://defang.io/samples), and [FAQ](/docs/category/faq) to know more. diff --git a/blog/2024-06-01-june-product-updates.md b/blog/2024-06-01-june-product-updates.md index f1ba56688e..b01e08573c 100644 --- a/blog/2024-06-01-june-product-updates.md +++ b/blog/2024-06-01-june-product-updates.md @@ -1,6 +1,6 @@ --- title: May 2024 Defang Compose Update -tags: [Cloud, NoDevOps, BYOC, Playground, Load Testing, ACME, Managed Redis, Kaniko, Postgres, ECS, Defang Compose Update] +tags: [Cloud, NoDevOps, BYOC, Load Testing, ACME, Managed Redis, Kaniko, Postgres, ECS, Defang Compose Update] authors: defang_team --- @@ -25,11 +25,11 @@ If you look through our [GitHub organization](https://github.com/DefangLabs), yo ![screenshot of github UI pointing towards template button](https://github.com/DefangLabs/defang-docs/assets/910895/97d33d90-43b9-499a-b139-e114b701adcb) -Not only will that create a new repo based on the sample in your account, but if you've used Defang before (and accepted the Terms and Conditions) it will automatically deploy it to the playground so you can start playing with Defang immediately. +Not only will that create a new repo based on the sample in your account, but if you've used Defang before (and accepted the Terms and Conditions) it will automatically deploy it so you can start playing with Defang immediately. ## ACME for BYOD -We’re excited to announce that ACME support is now available for Bring Your Own Domain (BYOD) in both Bring Your Own Cloud (BYOC) and Playground. This means you can easily add Let's Encrypt certificates to your custom domains, regardless of where your DNS is hosted. Defang will handle the certificate generation and automatic renewal for you. Nice and easy. +We’re excited to announce that ACME support is now available for Bring Your Own Domain (BYOD) in Bring Your Own Cloud (BYOC). This means you can easily add Let's Encrypt certificates to your custom domains, regardless of where your DNS is hosted. Defang will handle the certificate generation and automatic renewal for you. Nice and easy. ## Warnings for Stateful Services diff --git a/blog/2024-07-01-july-product-updates.md b/blog/2024-07-01-july-product-updates.md index e874535583..c52e321d4c 100644 --- a/blog/2024-07-01-july-product-updates.md +++ b/blog/2024-07-01-july-product-updates.md @@ -20,7 +20,7 @@ Deploying your apps from Windows just got a little bit nicer. ## One-click Deploy -We've added a new feature that will make it even easier to get started with Defang. We've created a flow where each sample provides a button that allows you to immediately deploy a template with a GitHub action which will automatically deploy the sample to the Defang Playground. That means you can easily make changes by committing them to your brand new repo, and everything automatically updates in the Playground. It's a great way to get started with Defang and start experimenting with your own projects. +We've added a new feature that will make it even easier to get started with Defang. We've created a flow where each sample provides a button that allows you to immediately deploy a template with a GitHub action which will automatically deploy the sample. That means you can easily make changes by committing them to your brand new repo, and everything automatically updates. It's a great way to get started with Defang and start experimenting with your own projects. Try it now [from our portal](https://portal.defang.dev/sample)! diff --git a/blog/2024-07-31-july-product-updates-2.md b/blog/2024-07-31-july-product-updates-2.md index 6f1021318a..c7ae565dc0 100644 --- a/blog/2024-07-31-july-product-updates-2.md +++ b/blog/2024-07-31-july-product-updates-2.md @@ -8,7 +8,7 @@ authors: defang_team Hey folks! We can’t believe a month has gone by already, time flies when you’re having fun! We continued to make progress on our vision of providing a radically simpler way to Develop, Deploy, and Debug cloud applications. In July, we spent time on a couple of key areas: -1. As our user-base grows, we wanted to make sure we’re able to scale our [Playground](/docs/concepts/defang-playground) environment to be able to handle the load. This involved being able to shard the workload across multiple ALBs and being able to dynamically move some workloads across shards where possible. With these changes, we are now able handle a large number of concurrent users comfortably. The only noticeable change in behavior you would see is that Defang will now ask you to “`compose down`” your previous project before you are able to deploy a new project on Playground. +1. As our user-base grows, we wanted to make sure we’re able to scale our infrastructure to handle the load. This involved being able to shard the workload across multiple ALBs and being able to dynamically move some workloads across shards where possible. With these changes, we are now able handle a large number of concurrent users comfortably. 2. The major news this month was the introduction of our “`debug`” functionality. The motivation for this feature was that while the Defang experience is amazing when everything goes smoothly, we saw users (including our own interns who are helping write all those [samples](https://defang.io/samples)) struggle when they hit an error. The underlying reason for the error could come from a variety of sources: an error in the developer’s application (including in their Dockerfile or Compose file), an issue in the way Defang is processing the application, or an issue in the underlying cloud platform (currently, AWS). To the developer, it is often not obvious what the issue is or how to fix it. That got us thinking how we could make this debugging experience “radically simpler” and thus the idea for `defang debug` was born. diff --git a/blog/2024-08-30-august-product-updates.md b/blog/2024-08-30-august-product-updates.md index c9aee7461f..5b57e8ab9f 100644 --- a/blog/2024-08-30-august-product-updates.md +++ b/blog/2024-08-30-august-product-updates.md @@ -29,7 +29,7 @@ Check it out [here](/docs/ask) or head to [ask.defang.io](https://ask.defang.io) ## Enhanced Platform Symmetry -We've been hard at work improving the symmetry between our Playground and BYOC environments as well as `docker compose up` vs `defang compose up` to provide a more seamless experience. You can now use multiple compose files and in BYOC the CLI will subscribe to events to monitor service health during deployments. +We've been hard at work improving our platform as well as the symmetry between `docker compose up` vs `defang compose up` to provide a more seamless experience. You can now use multiple compose files and in BYOC the CLI will subscribe to events to monitor service health during deployments. ## AI Features and Debugging Improvements diff --git a/blog/2024-09-30-september-product-updates.md b/blog/2024-09-30-september-product-updates.md index 3b0fc055d4..faae4f5a84 100644 --- a/blog/2024-09-30-september-product-updates.md +++ b/blog/2024-09-30-september-product-updates.md @@ -23,11 +23,11 @@ Hi everyone - you can feel the weather getting cooler, but things are heating up {/* truncate */} -1. **Bring-Your-Own-Cloud (BYOC) DigitalOcean in Preview!** From the very beginning, it has been part of Defang’s vision to not only provide a simpler way to develop, deploy, and debug your cloud applications, but to be able to do so in a portable way. As developers, we all value the flexibility of knowing our application can be deployed to our chosen cloud, even if that choice changes over time. Today, we take a big step in providing that choice with the Preview of BYOC with DigitalOcean! This literally means the same application can be deployed to the Defang Playground, AWS, or DigitalOcean with no changes! Take a look at the [docs](/docs/providers/digitalocean), give it a try and share your feedback on our [Discord](http://s.defang.io/discord). +1. **Bring-Your-Own-Cloud (BYOC) DigitalOcean in Preview!** From the very beginning, it has been part of Defang’s vision to not only provide a simpler way to develop, deploy, and debug your cloud applications, but to be able to do so in a portable way. As developers, we all value the flexibility of knowing our application can be deployed to our chosen cloud, even if that choice changes over time. Today, we take a big step in providing that choice with the Preview of BYOC with DigitalOcean! This literally means the same application can be deployed to AWS or DigitalOcean with no changes! Take a look at the [docs](/docs/providers/digitalocean), give it a try and share your feedback on our [Discord](http://s.defang.io/discord). 2. **Managed Postgres**: Postgres is one of the fundamental building blocks of many applications, and users wanted us to provide a way to add that to their application in a declarative way. So that’s exactly what we have done. You can now specify the Postgres image in your `compose.yaml` file and indicate that you want it managed by your cloud provider using `x-defang-postgres: true` in your service definition. Defang will automatically provision the appropriate managed Postgres in the target cloud (e.g. RDS on AWS) and do all the heavy lifting to configure and hook things up correctly. Check out the docs [here](/docs/concepts/managed-storage/managed-postgres), give it a try and let us know what you think. 3. We continue to improve the **quality and performance** of existing features: 1. We’ve made several improvements to our AI-assistant to increase the robustness of our Develop and Debug modules. For example, we updated generation to comply with latest Compose spec. We also addressed the top issues we saw people facing when deploying, such as out-of-memory errors when building containers. - 2. To cope with our growing user-base, we have made several scaling improvements to our Playground and Portal environments. + 2. To cope with our growing user-base, we have made several scaling improvements to our Portal environment. 3. We also made several updates to our documentation and samples to keep up with the changes and enhancements in the Defang product. --- diff --git a/blog/2024-11-13-october-product-updates.md b/blog/2024-11-13-october-product-updates.md index 8e3008360d..2c81b137e9 100644 --- a/blog/2024-11-13-october-product-updates.md +++ b/blog/2024-11-13-october-product-updates.md @@ -30,7 +30,7 @@ We are a little late getting our monthly update out this time, but we did ship a - Added `--wait` and `--wait-timeout` flags - Improved `generate` menu: all samples shown (previously these were restricted by language), and we moved the "Generate with AI" option to now be shown in the search filter. -2. **AI Debug for BYOC**: AI Debug feature is incredibly useful in helping users find and fix issues when something goes wrong. Our initial version only worked on Playground, but now we have extended this to BYOC environments. We hope this makes it even easier for you to deploy your apps to AWS, DigitalOcean, etc. +2. **AI Debug for BYOC**: AI Debug feature is incredibly useful in helping users find and fix issues when something goes wrong. We have extended this to all BYOC environments. We hope this makes it even easier for you to deploy your apps to AWS, DigitalOcean, etc. 3. A range of other **improvements**, including - Network `aliases` support diff --git a/blog/2025-02-07-january-product-updates.md b/blog/2025-02-07-january-product-updates.md index 459aab22fd..18e8642248 100644 --- a/blog/2025-02-07-january-product-updates.md +++ b/blog/2025-02-07-january-product-updates.md @@ -26,7 +26,7 @@ We are excited to build on that momentum going into 2025. And we are off to a gr {/* truncate */} 1. **GCP parity with AWS:** We are really excited to announce that our GCP provider is now feature-complete, with support for key features such as [Managed Postgres](/docs/concepts/managed-storage/managed-postgres), [Managed Redis](/docs/concepts/managed-storage/managed-redis), [BYOD](/docs/concepts/domains#bring-your-own-domain) (Bring-Your-Own-Domain), [GPUs](/docs/tutorials/deploy-with-gpu), AI-assisted [Debugging](/docs/concepts/debug), and more. Install the [latest version of our CLI](https://defang.io/#install) and give it a try! Please let us know your feedback. -2. **Defang Deployed with Defang:** In 2025, we are doubling our focus on production use-cases where developers are using Defang every day to deploy their production apps. And where better to start than with Defang itself? We had already been using Defang to deploy portions of our infrastructure (such as our web site), but we are super happy to report that now we are using Defang to deploy **all** our services - including our Portal, Playground, the Defang back-end (aka Fabric) and more. We’ll be sharing more about how we did this, and publishing some of the related artifacts, in a blog post soon - stay tuned. +2. **Defang Deployed with Defang:** In 2025, we are doubling our focus on production use-cases where developers are using Defang every day to deploy their production apps. And where better to start than with Defang itself? We had already been using Defang to deploy portions of our infrastructure (such as our web site), but we are super happy to report that now we are using Defang to deploy **all** our services - including our Portal, the Defang back-end (aka Fabric) and more. We’ll be sharing more about how we did this, and publishing some of the related artifacts, in a blog post soon - stay tuned. 3. **Campus Advocate Program:** One of our key goals for 2025 is to bring Defang to more students and hobbyists. To do this, we are very excited to launch our [Campus Advocate Program](https://defang.io/cap/), a community of student leaders passionate about cloud technology. Our advocates will build communities, host events, and help peers adopt cloud development with Defang. If you’re a student eager to drive cloud innovation on your campus, we’d love to hear from you - you can [apply here](https://s.defang.io/cap?_gl=1*1rx948d*_ga*ODk3NDgzNjU4LjE3MTgxNDc2MjQ.*_ga_QVJVWN44CW*MTczODM2NjYyOC4xMDMuMS4xNzM4MzY4MjI2LjAuMC4w). 4. **1-click Deploy instructions:** One of our most popular features is the ability to deploy any of our 50+ samples with [a single click](/docs/tutorials/using-one-click-deploy). We have now published [instructions](/docs/tutorials/adding-custom-one-click-deploy) showing how you can provide a similar experience for your project or sample. We are curious to see what you deploy with this! 5. **Model Context Protocol** sample: AI agents are of course the rage nowadays. Recently, Docker published a [blog](https://www.docker.com/blog/the-model-context-protocol-simplifying-building-ai-apps-with-anthropic-claude-desktop-and-docker/) showing how you can use Docker to containerize “servers” following Anthropic’s [Model Context Protocol](https://modelcontextprotocol.io/introduction). We have now published a sample that shows you how to easily deploy such containerized servers to the cloud using Defang - [check it out here](https://github.com/DefangLabs/samples/tree/main/samples/mcp). diff --git a/blog/2025-04-10-easiest-way-to-deploy-django.md b/blog/2025-04-10-easiest-way-to-deploy-django.md index 6f9183253d..d7fd1b6e3a 100644 --- a/blog/2025-04-10-easiest-way-to-deploy-django.md +++ b/blog/2025-04-10-easiest-way-to-deploy-django.md @@ -65,9 +65,7 @@ The Django admin is setup to quickly visualize messages and their moderation sta Deploying multi-service applications to cloud providers traditionally involves complex infrastructure setup, including configuring ECS clusters, security groups, networking, and more. Defang simplifies this significantly. -### Deploying to Defang Playground - -The Defang Playground lets you quickly preview your deployed app in a managed environment. +### Quick Deployment **Secure Configuration** diff --git a/blog/2025-04-23-vibe-deploy.md b/blog/2025-04-23-vibe-deploy.md index 261cdb3558..b45bb17c54 100644 --- a/blog/2025-04-23-vibe-deploy.md +++ b/blog/2025-04-23-vibe-deploy.md @@ -48,13 +48,13 @@ Once your app runs locally with these vibe coding tools, the next question is: h That is where [**Defang**](https://defang.io/) comes in. -Defang takes your app, as specified in your docker-compose.yml, and deploys it to the public cloud (AWS, GCP, or DigitalOcean) or the Defang Playground with a single command. It is already used by thousands of developers around the world to deploy their projects to the cloud. +Defang takes your app, as specified in your docker-compose.yml, and deploys it to the public cloud (AWS, GCP, or DigitalOcean) with a single command. It is already used by thousands of developers around the world to deploy their projects to the cloud. ![Defang Vibe Deploy](/img/vibe-deploy/defang-vibe-deploy.png) And now with the [Defang MCP Server](/docs/concepts/mcp), you can "vibe deploy" your project right from your favorite IDE! Once you have the Defang MCP Server installed (see instructions [here](/docs/concepts/mcp)), just type in "deploy" (or any variation thereof) in the chat, it's that simple! It is built for hobbyists, vibe coders, fast-moving teams, and AI-powered workflows. -Currently, we support deployment to the Defang [Playground](/docs/concepts/defang-playground) only, but we'll be adding deployment to public cloud soon. +The Defang MCP Server supports deployment to your cloud of choice. **How it works:** diff --git a/blog/2025-06-06-may-product-updates.md b/blog/2025-06-06-may-product-updates.md index af336fbfea..841c16a900 100644 --- a/blog/2025-06-06-may-product-updates.md +++ b/blog/2025-06-06-may-product-updates.md @@ -19,17 +19,15 @@ authors: defang_team ![Defang Compose Update](/img/defang-compose-update.webp) -May was a big month at Defang. We shipped support for managed LLMs in Playground, added MongoDB support on AWS, improved the Defang MCP Server, and dropped new AI samples to make deploying faster than ever. +May was a big month at Defang. We shipped support for managed LLMs, added MongoDB support on AWS, improved the Defang MCP Server, and dropped new AI samples to make deploying faster than ever. {/* truncate */} -## 🚀 Managed LLMs in Playground +## 🚀 Managed LLMs -You can now try managed LLMs directly in the Defang Playground. -Defang makes it easy to use cloud-native language models across providers — and now you can test them instantly in the Playground. +Defang makes it easy to use cloud-native language models across providers. -- Managed LLM support -- Playground-ready +- Managed LLM support across AWS, GCP, and more - Available in CLI v1.1.22 or higher To use managed language models in your own Defang services, just add `x-defang-llm: true` — Defang will configure the appropriate roles and permissions for you. diff --git a/blog/2025-06-16-crew-ai-sample.md b/blog/2025-06-16-crew-ai-sample.md index b76ffb1120..a3d205c6ca 100644 --- a/blog/2025-06-16-crew-ai-sample.md +++ b/blog/2025-06-16-crew-ai-sample.md @@ -9,7 +9,7 @@ authors: defang_team Let’s be honest: every developer who’s played with LLMs gets that rush of “wow” from the first working demo. But the real headaches show up when you need to stitch LLMs into something production-grade: an app that can pull in real data, coordinate multi-step logic, and more. Suddenly, you’re not just writing single prompts. You’re coordinating between multiple prompts, managing queues, adding vector databases, orchestrating workers, and trying to get things back to the user in real-time. We've found that [CrewAI](https://www.crewai.com/) (coordinating prompts, agents, tools) + [Django](https://www.djangoproject.com/) (building an api, managing data), with a bit of [Celery](https://docs.celeryproject.org/en/stable/) (orchestrating workers/async tasks), is a really nice set of tools for this. We're also going to use [Django Channels](https://channels.readthedocs.io/en/stable/) (real-time updates) to push updates back to the user. And of course, we'll use [Defang](https://www.defang.io/) to deploy all that to the cloud. -If this sounds familiar (or if you're dreading the prospect of dealing with it), you’re the target audience for this sample. Instead of slogging through weeks of configuration and permissions hell, you get a ready-made template that runs on your laptop, then scales—unchanged—to Defang’s Playground, and finally to your own AWS or GCP account. All the gnarly infra is abstracted, so you can focus on getting as much value as possible out of that magical combo of CrewAI and Django. +If this sounds familiar (or if you're dreading the prospect of dealing with it), you’re the target audience for this sample. Instead of slogging through weeks of configuration and permissions hell, you get a ready-made template that runs on your laptop, then scales—unchanged—to your own AWS or GCP account with Defang. All the gnarly infra is abstracted, so you can focus on getting as much value as possible out of that magical combo of CrewAI and Django. :::info[Just want the sample?] You can [find it here](https://github.com/DefangSamples/sample-crew-django-redis-postgres-template). @@ -63,7 +63,7 @@ In local dev, your `compose.local.yaml` spins up [Gemma](https://hub.docker.com/ ## The Three-Step Deployment Journey -You can run everything on your laptop with a single `docker compose -f ./compose.local.yaml up` command—no cloud dependencies, fast iteration, and no risk of cloud charges. When you’re ready for the next step, use `defang compose up` to push to the Defang Playground. This free hosted sandbox is perfect for trying Defang, demos, or prototyping. It automatically adds TLS to your endpoints and sleeps after a week. For production, use your own AWS or GCP account. `DEFANG_PROVIDER=aws defang compose up` maps each service to a managed equivalent (ECS, RDS, ElastiCache, Bedrock models), wires up secrets, networking, etc. Your infra. Your data. +You can run everything on your laptop with a single `docker compose -f ./compose.local.yaml up` command—no cloud dependencies, fast iteration, and no risk of cloud charges. When you’re ready to deploy, use your own AWS or GCP account. `DEFANG_PROVIDER=aws defang compose up` maps each service to a managed equivalent (ECS, RDS, ElastiCache, Bedrock models), wires up secrets, networking, etc. Your infra. Your data. ## Some Best Practices and Design Choices @@ -82,8 +82,6 @@ Quickstart: ```shell # Local docker compose -f compose.local.yaml up --build -# Playground -defang compose up # BYOC # Setup credentials and then swap with aws or gcp DEFANG_PROVIDER= defang compose up diff --git a/blog/2025-07-10-june-product-updates.md b/blog/2025-07-10-june-product-updates.md index 84c93164cd..49ad771b8b 100644 --- a/blog/2025-07-10-june-product-updates.md +++ b/blog/2025-07-10-june-product-updates.md @@ -20,7 +20,7 @@ authors: defang_team ![Defang Compose Update](/img/defang-compose-update.webp) -June was a big month at Defang. We rolled out powerful features across our CLI, Playground, and Portal, expanded support for both AWS and GCP, and introduced new tools to help you ship faster and smarter. From real-time cloud cost estimation to internal infra upgrades and community highlights, here’s everything we accomplished. +June was a big month at Defang. We rolled out powerful features across our CLI and Portal, expanded support for both AWS and GCP, and introduced new tools to help you ship faster and smarter. From real-time cloud cost estimation to internal infra upgrades and community highlights, here’s everything we accomplished. {/* truncate */} @@ -43,9 +43,9 @@ Whether you’re building a smart Q&A tool or a multi-agent research assistant, We’ve added active deployment information to the Defang Portal. You can now see your currently active deployments across various cloud providers and understand the details of each, while still managing your cloud environments through the provider’s own tools (e.g. the AWS Console). -## ☁️ Playground Now Runs on AWS + GCP +## ☁️ Multi-Cloud Infrastructure Milestone -Internally, we also hit a big milestone: The Defang Playground now runs on both AWS and GCP, showing the power of Defang’s multi-cloud infrastructure. We’ve also enabled load balancing between the two platforms and plan to share a detailed blog post on how it works soon. +Internally, we also hit a big milestone: our infrastructure now runs on both AWS and GCP, showing the power of Defang’s multi-cloud capabilities. We’ve also enabled load balancing between the two platforms and plan to share a detailed blog post on how it works soon. ## 🧩 VS Code Extension Released diff --git a/blog/2025-08-07-defang-ai-devops-agent.md b/blog/2025-08-07-defang-ai-devops-agent.md index 42674d12b4..501b3047d9 100644 --- a/blog/2025-08-07-defang-ai-devops-agent.md +++ b/blog/2025-08-07-defang-ai-devops-agent.md @@ -40,7 +40,7 @@ Whether you're launching a side project or scaling a multi-agent app, **Defang** - **Secure and Scalable:** Built-in TLS, secrets, autoscaling, IAM, and HTTPS - **Multi-Cloud Ready:** Deploy to your cloud (AWS, GCP, DO) using your own credentials - **Language & framework agnostic:** Next.js, Go, Python (Django/Flask), C#, … -- **Managed LLM:** Add `x-defang-llm: true` and **Defang** auto-configures cloud-native LLMs like Bedrock, Vertex AI, and the Defang Playground +- **Managed LLM:** Add `x-defang-llm: true` and **Defang** auto-configures cloud-native LLMs like Bedrock and Vertex AI - **Configures managed services** (e.g. managed Postgres, MongoDB, Redis) using the target cloud's native services (e.g. RDS for Postgres on AWS, Cloud SQL on GCP). - **Tailored deployment modes** (e.g. affordable, balance, high-availability) optimized for different environments (dev, staging, production) - **AI Debugging:** Get context-aware assistance to quickly identify and fix deployment issues diff --git a/blog/2025-08-22-agentic-apps.md b/blog/2025-08-22-agentic-apps.md index 47ecc5a09e..e69067ebf7 100644 --- a/blog/2025-08-22-agentic-apps.md +++ b/blog/2025-08-22-agentic-apps.md @@ -57,8 +57,7 @@ Agentic apps need to be fast, secure, and ready to scale. Defang delivers cloud- ## The Developer Journey, Simplified 1. Build your agentic app locally using Docker Compose -2. Test in Defang's free playground with `defang compose up` -3. Deploy to your cloud: +2. Deploy to your cloud: ```bash defang compose up --provider=aws # or gcp, digitalocean diff --git a/blog/2025-09-09-august-product-updates.md b/blog/2025-09-09-august-product-updates.md index c6839527c5..de00a20aae 100644 --- a/blog/2025-09-09-august-product-updates.md +++ b/blog/2025-09-09-august-product-updates.md @@ -21,7 +21,7 @@ authors: defang_team ![Defang Compose Update](/img/defang-compose-update.webp) -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. +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 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. {/* truncate */} @@ -31,7 +31,7 @@ As more and more teams are moving away from legacy PaaS solutions, looking for m ## 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. +We expanded and refined our sample projects for agentic frameworks like CrewAI, LangGraph, Autogen, and Strands, validating across 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 @@ -43,7 +43,7 @@ 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. +[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 your cloud. Net result: you can ship no-Dockerfile apps across clouds with less setup and fewer surprises. ## Events and Community diff --git a/blog/2025-10-17-september-product-updates.md b/blog/2025-10-17-september-product-updates.md index af71d910a0..f2b8494288 100644 --- a/blog/2025-10-17-september-product-updates.md +++ b/blog/2025-10-17-september-product-updates.md @@ -42,7 +42,7 @@ We've also improved certificate management and simplified networking by removing Our VS Code extension is now verified on the Marketplace, and we've built MCP setup directly into the installer for easier onboarding. CLI authentication has moved from localhost to auth.defang.io, enabling full compatibility with Docker containers and GitHub Codespaces. -Public DNS now auto-fills in Compose files, saving you time during configuration. We've also expanded MCP tools to include logs, BYOC, and Playground provider support. +Public DNS now auto-fills in Compose files, saving you time during configuration. We've also expanded MCP tools to include logs and BYOC provider support. ## Documentation and Tutorials diff --git a/docs/concepts/accounts.md b/docs/concepts/accounts.md index 97f6ce15f0..339ff7b311 100644 --- a/docs/concepts/accounts.md +++ b/docs/concepts/accounts.md @@ -7,7 +7,7 @@ description: How accounts are organized in Defang. Below, we will cover account creation with Defang, and how resources are organized within a cloud environment using your account info. -Defang requires an account so we can organize your resources and provide you with a way to manage them. We also use your account to authenticate you when you interact with [Defang Playground](./defang-playground.md) and the [Defang Portal](./portal.md). Billing and payment information is also associated with your account. +Defang requires an account so we can organize your resources and provide you with a way to manage them. We also use your account to authenticate you when you interact with the [Defang Portal](./portal.md). Billing and payment information is also associated with your account. ## Creating an Account @@ -34,7 +34,7 @@ For more information, see [Workspaces](./workspaces.md). Your GitHub username will be used as your Defang username. Your Defang username is used to group all your [services](/docs/concepts/services) and generate domains for your services with the following structure: ``` ----.prod1.defang.dev +--...defang.app ``` For more about domain structures, see our [Domains](/docs/concepts/domains#structure) page. diff --git a/docs/concepts/configuration.md b/docs/concepts/configuration.md index c89d2fe516..9b519ac2c2 100644 --- a/docs/concepts/configuration.md +++ b/docs/concepts/configuration.md @@ -107,7 +107,6 @@ Please note that while Defang supports setting sensitive config, it does not sup | Provider | Config Support | |----------------|:--------------:| -| Playground | ✅ | | AWS | ✅ | | DigitalOcean | ✅ | | GCP | ✅ | diff --git a/docs/concepts/defang-byoc.md b/docs/concepts/defang-byoc.md index e1043bedcc..f44b436ff9 100644 --- a/docs/concepts/defang-byoc.md +++ b/docs/concepts/defang-byoc.md @@ -5,7 +5,7 @@ description: Defang allows you deploy services, defined as containers, to your o # Defang BYOC -Defang aims to make it easier to deploy your services to the cloud. Specifically, Defang's goal is to make it easier to deploy your workloads to your *own* cloud accounts. We refer to this as bring-your-own-cloud (BYOC). We also provide Defang Playground, but it is only intended for non-production workloads so you can get a feel for how Defang works. +Defang aims to make it easier to deploy your services to the cloud. Specifically, Defang's goal is to make it easier to deploy your workloads to your *own* cloud accounts. We refer to this as bring-your-own-cloud (BYOC). Defang provisions and configures the necessary native managed services from your cloud provider to get your services up and running. For example, on AWS, Defang will configure an [ALB](https://aws.amazon.com/elasticloadbalancing/application-load-balancer/), set up [ECR](https://aws.amazon.com/ecr/), configure [CloudWatch](https://aws.amazon.com/cloudwatch/?nc2=type_a), and run your service on [ECS](https://aws.amazon.com/ecs/?nc2=type_a) and more. The following lists the existing and planned support for cloud providers. @@ -19,8 +19,7 @@ Defang does run the Defang build service to build your container images, which t The Defang CLI can be configured to deploy to a cloud provider either by using the `--provider` flag or by setting the `DEFANG_PROVIDER` environment variable. For example: ```bash -# Supported provider values: auto, aws, defang, digitalocean -# Default is auto, which deploys to the Defang Playground but warns if it detects cloud credentials +# Supported provider values: auto, aws, digitalocean $ defang compose up --provider=aws # or $ export DEFANG_PROVIDER=digitalocean diff --git a/docs/concepts/defang-playground.md b/docs/concepts/defang-playground.md deleted file mode 100644 index 99353c393d..0000000000 --- a/docs/concepts/defang-playground.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Defang Playground -description: Defang Playground allows you to get a feel for how Defang works without running production workloads in your own cloud accounts. ---- - -# Defang Playground - -Defang aims to make it easier to deploy your services to the cloud. Specifically, Defang's goal is to make it easier to deploy your workloads to your *own* cloud accounts. We refer to this as bring-your-own-cloud (BYOC) which you can read about in more depth [here](./defang-byoc). We also provide Defang Playground, but it is only intended for non-production workloads so you can get a feel for how Defang works. - -Defang Playground is a free tier that allows you to deploy services to a Defang-hosted cloud account without needing to manage your own. It is intended for non-production workloads only. - -:::warning -Please note that the Defang Playground is intended for testing/learning purposes only. The environment may be reset at any time. Do not run production workloads in Defang Playground. -::: - -## Limitations - -There are a few limitations to Defang Playground. These limitations are in place to ensure that Defang Playground is only used for non-production workloads. If you are interested in running production workloads, you should use Defang BYOC. - -### No Apex Domain Support - -When you deploy a service to Defang Playground, it will be assigned a domain under the `defang.dev` domain. We do not support pointing your own apex domains to Defang Playground services, but you can use subdomains. - -### Max Resources - -* Projects: 1 -* Services: 4 -* CPUs: 2 -* Memory: 1GiB -* Replicas: 1 diff --git a/docs/concepts/deployments.md b/docs/concepts/deployments.md index 0a01288d3d..19eef5f78a 100644 --- a/docs/concepts/deployments.md +++ b/docs/concepts/deployments.md @@ -5,7 +5,7 @@ description: Defang will build your services in the cloud and manage the deploym # Deployment -When you deploy using Defang, whether it's with `defang compose up` with a [Compose file](./compose.md) or using a [Pulumi program](./pulumi.md), Defang will build your services in the cloud and manage the deployment process for you. If you provide a Dockerfile and build context, Defang will upload the files found within the build context to the cloud (either yours in [Defang BYOC](./defang-byoc.md) or ours in [Defang Playground](./defang-playground.md)), build the image, and store it in the cloud provider's container registry. +When you deploy using Defang, whether it's with `defang compose up` with a [Compose file](./compose.md) or using a [Pulumi program](./pulumi.md), Defang will build your services in the cloud and manage the deployment process for you. If you provide a Dockerfile and build context, Defang will upload the files found within the build context to your cloud account via [Defang BYOC](./defang-byoc.md), build the image, and store it in the cloud provider's container registry. ## Deploying Updates @@ -18,7 +18,7 @@ Defang can deploy your services using different [modes](/docs/concepts/deploymen By default, using the `affordable` mode, Defang will deprovision your existing services before provisioning replacements. This helps reduce costs. :::info -In [Defang BYOC](./defang-byoc.md), Defang uses your cloud provider account to build and store your images. In [Defang Playground](./defang-playground.md), we build and store your images for you. +In [Defang BYOC](./defang-byoc.md), Defang uses your cloud provider account to build and store your images. ::: diff --git a/docs/concepts/domains.mdx b/docs/concepts/domains.mdx index 110bbc0d94..508579cc66 100644 --- a/docs/concepts/domains.mdx +++ b/docs/concepts/domains.mdx @@ -17,22 +17,11 @@ To make your service accessible from the public internet with Defang-hosted doma Defang-hosted domains use a structure that is based on your username and service name. - - -If you have a publicly accessible service, you will automatically receive a domain to access it. If you're deploying to the [Defang Playground](./defang-playground.md), your domain will be structured as follows: - -``` -https://---.defang.dev -``` - - -If you're using [Defang BYOC](./defang-byoc.md), your domain will be: +If you have a publicly accessible service, you will automatically receive a domain to access it. When using [Defang BYOC](./defang-byoc.md), your domain will be structured as follows: ``` https://--...defang.app ``` - - ### Sample Configuration @@ -72,9 +61,9 @@ const service = new defang.DefangService("serviceName", { You can also bring your own domain to a Defang project. This allows you to use your own domain name to access your services, and varies a little bit depending on your setup. -### BYOC or Defang Playground +### BYOC without Cloud-hosted DNS -If you are using [Defang BYOC](./defang-byoc.md) and *do not* have your domain's DNS hosted with your cloud provider, or if you are using the [Defang Playground](./defang-playground.md), you will need to follow this flow: +If you are using [Defang BYOC](./defang-byoc.md) and *do not* have your domain's DNS hosted with your cloud provider, you will need to follow this flow: 1. Add the `domainname` to your service definition. 2. Run `defang compose up` to deploy your project. @@ -109,7 +98,7 @@ services: :::warning -As of now, the Pulumi provider does not support [Defang BYOC](./defang-byoc.md) and the [Defang Playground](./defang-playground.md) does not support bringing your own domain, since it is not for production use. +As of now, the Pulumi provider does not support [Defang BYOC](./defang-byoc.md). ::: @@ -118,7 +107,6 @@ As of now, the Pulumi provider does not support [Defang BYOC](./defang-byoc.md) | Provider | BYOD | | --- | --- | -| [Playground](/docs/providers/playground) | ✅ no apex domains | | [AWS](/docs/providers/aws) | ✅ | | [DigitalOcean](/docs/providers/digitalocean) | ❌ | | [GCP](/docs/providers/gcp) | ✅ | diff --git a/docs/concepts/estimation.md b/docs/concepts/estimation.md index f9e60f4b54..1390e683d8 100644 --- a/docs/concepts/estimation.md +++ b/docs/concepts/estimation.md @@ -67,7 +67,6 @@ defang compose up [--provider aws|gcp|digitalocean] [--mode affordable|balanced| | Provider | Estimation Support | |----------------|:------------------:| -| Playground | ❌ | | AWS | ✅ | | DigitalOcean | ❌ | | GCP | ✅ | diff --git a/docs/concepts/managed-llms/managed-language-models.md b/docs/concepts/managed-llms/managed-language-models.md index 7983594a97..63459eab2d 100644 --- a/docs/concepts/managed-llms/managed-language-models.md +++ b/docs/concepts/managed-llms/managed-language-models.md @@ -11,7 +11,6 @@ Each cloud provider offers their own managed Large Language Model services. AWS | Provider | Managed Language Models | | --- | --- | -| [Playground](/docs/providers/playground#managed-llms) | ✅ | | [AWS Bedrock](/docs/providers/aws#managed-llms) | ✅ | | [DigitalOcean GenAI](/docs/providers/digitalocean#future-improvements) | ❌ | | [GCP Vertex AI](/docs/providers/gcp#managed-llms) | ✅ | @@ -45,6 +44,3 @@ Defang has a [*Managed LLM sample*](https://github.com/DefangLabs/samples/tree/m ::: -## Managed LLM on Playground -If you are using the Managed LLM feature on [Defang Playground](/docs/concepts/defang-playground), please note that your `MODEL` (model ID) will be limited to a default model chosen by Defang. -To access a full range of models, consider using [Defang BYOC](/docs/concepts/defang-byoc). diff --git a/docs/concepts/managed-llms/openai-access-gateway.md b/docs/concepts/managed-llms/openai-access-gateway.md index c41b22af34..1795612ffd 100644 --- a/docs/concepts/managed-llms/openai-access-gateway.md +++ b/docs/concepts/managed-llms/openai-access-gateway.md @@ -46,7 +46,6 @@ This can be configured through the following environment variables: | Provider | Managed Language Models | | --- | --- | -| [Playground](/docs/providers/playground#managed-services) | ✅ | | [AWS Bedrock](/docs/providers/aws#managed-llms) | ✅ | | [DigitalOcean GenAI](/docs/providers/digitalocean#future-improvements) | ❌ | | [GCP Vertex AI](/docs/providers/gcp#managed-llms) | ✅ | diff --git a/docs/concepts/managed-storage/managed-mongodb.md b/docs/concepts/managed-storage/managed-mongodb.md index 9c636539b2..b20d24e89b 100644 --- a/docs/concepts/managed-storage/managed-mongodb.md +++ b/docs/concepts/managed-storage/managed-mongodb.md @@ -15,7 +15,6 @@ Managed MongoDB is a service that allows you to store and retrieve large amounts | Provider | Managed MongoDB | | --- | --- | -| [Playground](/docs/providers/playground#managed-services) | ⚠️ Unmanaged | | [AWS](/docs/providers/aws#managed-storage) | ✅ DocumentDB | | [DigitalOcean](/docs/providers/digitalocean#future-improvements) | ⚠️ Unmanaged | | [GCP](/docs/providers/gcp#future-improvements) | ✅ Firestore | diff --git a/docs/concepts/managed-storage/managed-object-storage.md b/docs/concepts/managed-storage/managed-object-storage.md index 88fd2e7cc9..36f78c45a9 100644 --- a/docs/concepts/managed-storage/managed-object-storage.md +++ b/docs/concepts/managed-storage/managed-object-storage.md @@ -15,7 +15,6 @@ Managed Object Storage, like AWS S3, is a service that allows you to store and r | Provider | Managed Object Storage | | --- | --- | -| [Playground](/docs/providers/playground#managed-services) | ❌ | | [AWS](/docs/providers/aws#managed-storage) | ❌ | | [DigitalOcean](/docs/providers/digitalocean#future-improvements) | ❌ | | [GCP](/docs/providers/gcp#future-improvements) | ❌ | diff --git a/docs/concepts/managed-storage/managed-postgres.mdx b/docs/concepts/managed-storage/managed-postgres.mdx index 6ef82b9187..588bcba715 100644 --- a/docs/concepts/managed-storage/managed-postgres.mdx +++ b/docs/concepts/managed-storage/managed-postgres.mdx @@ -11,7 +11,6 @@ Postgres, or PostgreSQL, is a powerful open-source relational database system kn | Provider | Managed Postgres | | --- | --- | -| [Playground](/docs/providers/playground#managed-services) | ⚠️ Unmanaged | | [AWS](/docs/providers/aws#managed-storage) | ✅ RDS Postgres | | [DigitalOcean](/docs/providers/digitalocean#future-improvements) | ⚠️ Unmanaged | | [GCP](/docs/providers/gcp#managed-storage) | ✅ Cloud SQL Postgres | diff --git a/docs/concepts/managed-storage/managed-redis.md b/docs/concepts/managed-storage/managed-redis.md index a5044d64d3..395fc6b4a0 100644 --- a/docs/concepts/managed-storage/managed-redis.md +++ b/docs/concepts/managed-storage/managed-redis.md @@ -11,7 +11,6 @@ Redis is an in-memory data structure store widely used for caching, real-time an | Provider | Managed Redis | | --- | --- | -| [Playground](/docs/providers/playground#managed-services) | ⚠️ Unmanaged | | [AWS](/docs/providers/aws#managed-storage) | ✅ Elasticache | | [DigitalOcean](/docs/providers/digitalocean#future-improvements) | ⚠️ Unmanaged | | [GCP](/docs/providers/gcp#managed-redis) | ✅ Memorystore | diff --git a/docs/concepts/networking.mdx b/docs/concepts/networking.mdx index b774bd0c15..43ed7eee97 100644 --- a/docs/concepts/networking.mdx +++ b/docs/concepts/networking.mdx @@ -2,8 +2,6 @@ title: Networking description: Defang helps you safely configure your services' networking. --- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; # Networking @@ -106,26 +104,11 @@ services: ### Internal DNS -Internal communication is handled slightly differently between the Defang Playground and Defang BYOC. - - - -Internal communication between services in the Defang Playground follows the following pattern: - -``` -http://-: -``` - -The Defang CLI applies the `` prefix when it detects service names in the values of environment variables. - - -Internal communication between services in Defang BYOC follows the following pattern: +Internal communication between services follows this pattern: ``` http://: ``` - - ### Custom Network CIDR diff --git a/docs/concepts/observability.md b/docs/concepts/observability.md index 67c64f2dcd..405e8b7333 100644 --- a/docs/concepts/observability.md +++ b/docs/concepts/observability.md @@ -13,9 +13,6 @@ When you deploy a service using the `defang compose up`, the CLI will automatica Defang has a tutorial on how you can [monitor your services' status and logs](/docs/tutorials/monitoring-your-services). ::: -:::warning -Keep in mind that the [Defang Portal](./portal.md) only displays services deployed to Defang Playground. -::: ## Tail diff --git a/docs/concepts/one-off-jobs.md b/docs/concepts/one-off-jobs.md index fa00947cff..1434b3d3da 100644 --- a/docs/concepts/one-off-jobs.md +++ b/docs/concepts/one-off-jobs.md @@ -137,7 +137,6 @@ One off jobs are deployed as temporary containers on the same infrastructure as | Provider | Release Task Support | |----------------|:--------------------:| -| Playground | ✅ | | AWS | ✅ | | DigitalOcean | ❌ | | GCP | ✅ | diff --git a/docs/concepts/portal.md b/docs/concepts/portal.md index 5150d10734..ba88619bb6 100644 --- a/docs/concepts/portal.md +++ b/docs/concepts/portal.md @@ -5,15 +5,10 @@ description: You can log into the Defang Portal to view the state of your Defang # Portal -You can log into the Defang Portal at [portal.defang.dev](https://portal.defang.dev) using your [Defang account](./accounts.md) to view the state of your Defang services running in the Defang Playground for non-production applications. +You can log into the Defang Portal at [portal.defang.dev](https://portal.defang.dev) using your [Defang account](./accounts.md) to view the state of your Defang services. You can use the Portal to get an overview of your [services](/docs/concepts/services), view the logs for each service, quickly access exposed ports, view environment variables, and more. The Portal is also where you manage your [workspaces](./workspaces.md), invite team members, and configure billing. -:::info -The Defang Portal displays services deployed to Defang Playground. -To view services deployed to Defang BYOC, please check out [Monitoring Your Services](/docs/tutorials/monitoring-your-services). -::: - :::tip Need help with a failing deployment? Defang provides a tool to help [debug](/docs/concepts/debug) in your application. ::: diff --git a/docs/concepts/pulumi.md b/docs/concepts/pulumi.md index 02a96a4428..ac8ed0df18 100644 --- a/docs/concepts/pulumi.md +++ b/docs/concepts/pulumi.md @@ -9,7 +9,7 @@ import TabItem from '@theme/TabItem'; # Pulumi :::warning -Pulumi support is currently only available for Defang Playground. We are working on support for Defang BYOC. +Pulumi support is currently only available for deploying to Defang's infrastructure. We are working on support for Defang BYOC. ::: [Pulumi](https://www.pulumi.com) is a modern infrastructure-as-code toolkit that allows developers to use a programming language like Typescript to provision and manage cloud resources. diff --git a/docs/concepts/railpack.md b/docs/concepts/railpack.md index deb4966518..7e80ef7d99 100644 --- a/docs/concepts/railpack.md +++ b/docs/concepts/railpack.md @@ -148,7 +148,6 @@ services: | Provider | Railpack Support | |----------------|:----------------:| -| Playground | ✅ | | AWS | ✅ | | DigitalOcean | ❌ | | GCP | ✅ | diff --git a/docs/concepts/scaling.md b/docs/concepts/scaling.md index 485b9d0b75..53615b4b4e 100644 --- a/docs/concepts/scaling.md +++ b/docs/concepts/scaling.md @@ -68,7 +68,6 @@ Auto-scaling systems typically rely on: | Provider | Auto-Scaling Support | |----------------|:--------------------:| -| Playground | ❌ | | AWS | ✅ | | DigitalOcean | ❌ | | GCP | ✅ | diff --git a/docs/concepts/services.md b/docs/concepts/services.md index 9c21054fbf..d6c05ca768 100644 --- a/docs/concepts/services.md +++ b/docs/concepts/services.md @@ -3,8 +3,6 @@ title: Services description: Defang allows you to deploy services, defined as containers, to the cloud. --- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; # Services @@ -19,20 +17,11 @@ Defang identifies services by using your [account username](/docs/concepts/accou Service names are defined in your Compose file or in your Pulumi program. ::: - - - Domains for services in Playground follow the following pattern: - ``` - ---.prod1a.defang.dev - ``` - - - Domains for services in Defang BYOC follow the following pattern: - ``` - --...defang.app - ``` - - +Domains for services follow this pattern: + +``` +--...defang.app +``` ### Service Deployment diff --git a/docs/intro/faq/questions.md b/docs/intro/faq/questions.md index 0eeb87942f..4a43b4f98b 100644 --- a/docs/intro/faq/questions.md +++ b/docs/intro/faq/questions.md @@ -11,7 +11,7 @@ import {Button, ButtonGroup, FormGroup, FormLabel} from "@mui/material" ### Which cloud/region is the app being deployed to? -- In the [Defang Playground](/docs/concepts/defang-playground), the app is deployed to AWS `us-west-2`. In the [Defang BYOC](/docs/concepts/defang-byoc) model, the region is determined by your Defang BYOC [Provider](/docs/providers) settings. +- The region is determined by your [Defang BYOC](/docs/concepts/defang-byoc) [Provider](/docs/providers) settings. ### Can I bring my own AWS or other cloud account? @@ -66,10 +66,10 @@ import {Button, ButtonGroup, FormGroup, FormLabel} from "@mui/material" ## Feature Comparisons ### Is Defang a run-time platform? -- No. Defang is not a run-time platform. Instead, it lets you host and run your application on a [cloud provider](/docs/providers) of your choice. You can think of it as a tool that makes it way easier to deploy to that cloud provider. We do provide [Defang Playground](/docs/concepts/defang-playground), but it is meant to be used as a testing environment only. +- No. Defang is not a run-time platform. Instead, it lets you host and run your application on a [cloud provider](/docs/providers) of your choice. You can think of it as a tool that makes it way easier to deploy to that cloud provider. ### What is the difference between Defang and platforms such as Vercel, fly.io, Railway, Render, or Heroku? -- Defang is a tool that helps you get your application deployed to a [cloud provider](/docs/providers) of your choice, and it is not a platform. Unlike platforms, Defang does not host your application. We do provide [Defang Playground](/docs/concepts/defang-playground), but it is meant to be used as a testing environment only. +- Defang is a tool that helps you get your application deployed to a [cloud provider](/docs/providers) of your choice, and it is not a platform. Unlike platforms, Defang does not host your application. ### What is the difference between Defang and tools such as SST? - Defang is cloud-agnostic and language-agnostic, meaning that it is designed to work with different [cloud providers](/docs/providers), and programming languages. Since Defang is not tied to just one cloud or language, this allows for greater flexibility in a wide range of cases. Another difference is that Defang follows the [Compose specification](https://docs.docker.com/compose/compose-file/), allowing it to work smoothly with various container platforms such as Docker. diff --git a/docs/intro/getting-started.mdx b/docs/intro/getting-started.mdx index f0d85b1e99..cf1d14114d 100644 --- a/docs/intro/getting-started.mdx +++ b/docs/intro/getting-started.mdx @@ -106,7 +106,7 @@ You can open the folder in your favorite editor and see the files that were gene * The `Dockerfile` is used to build the container image for your service. * The `compose.yaml` file is used to define the services you want to deploy. -## Deploy to the Playground +## Deploy Go back to your shell and type the following: @@ -138,7 +138,7 @@ When you do this, you should see something similar to the output below: 2024-09-19T10:51:05.536299-07:00 cd Update succeeded in 11.99769745s ; provisioning... 2024-09-19T10:51:39.419693-07:00 app Server running at http://0.0.0.0:3000/ * Service app is in state DEPLOYMENT_COMPLETED and will be available at: - - https://jordanstephens-app--3000.prod1.defang.dev + - https://app--3000.prod1.jordanstephens.defang.app * Done. ``` diff --git a/docs/intro/intro.mdx b/docs/intro/intro.mdx index a25af42aad..15194bf6f5 100644 --- a/docs/intro/intro.mdx +++ b/docs/intro/intro.mdx @@ -30,17 +30,11 @@ import DocCardList from "@docusaurus/theme-classic/lib/theme/DocCardList"; label: "CLI Reference", description: "Use the Defang CLI to deploy your app", }, - { - type: "link", - href: "/docs/tutorials/deploy-to-playground", - label: "Try Defang", - description: "Deploy to our free Playground", - }, { type: "link", href: "/docs/tutorials/deploy-to-your-cloud", - label: "Deploy to your own cloud", - description: "When you're ready for production", + label: "Deploy to your cloud", + description: "Deploy to your own cloud account", }, ]} /> diff --git a/docs/intro/what-is-defang.mdx b/docs/intro/what-is-defang.mdx index ec0be9ad85..29d0c2f00a 100644 --- a/docs/intro/what-is-defang.mdx +++ b/docs/intro/what-is-defang.mdx @@ -22,8 +22,7 @@ The [Defang CLI (command line interface)](/docs/intro/getting-started#install-th Defang can automatically build and deploy your project with a single command. - - If you’re new to Defang, you can try deploying to [Defang Playground](/docs/concepts/defang-playground.md), a hosted environment to learn to use Defang with non-production workloads. - - Once you’re ready, you can [deploy](/docs/tutorials/deploy-to-your-cloud) a project to your own cloud account - we call this [Defang BYOC (Bring-your-Own-Cloud)](/docs/concepts/defang-byoc.md). We offer support for the following cloud providers: + - You can [deploy](/docs/tutorials/deploy-to-your-cloud) a project to your own cloud account - we call this [Defang BYOC (Bring-your-Own-Cloud)](/docs/concepts/defang-byoc.md). We offer support for the following cloud providers: * [Amazon Web Services (AWS)](/docs/tutorials/deploy-to-aws) * [DigitalOcean](/docs/tutorials/deploy-to-digitalocean) * [Google Cloud Platform (GCP)](/docs/tutorials/deploy-to-gcp) diff --git a/docs/providers/playground.md b/docs/providers/playground.md deleted file mode 100644 index ae70a9e1dc..0000000000 --- a/docs/providers/playground.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Playground -description: The Defang Playground is a free tier that allows you to experiment with Defang. -sidebar_position: 10 ---- - -The Defang Playground is a free deployment provider that allows you to experiment with Defang. The Playground is a shared environment that should not be used to run production workloads. The Playground is a great way to get started with Defang. You can even use [1-Click Deploy](/docs/tutorials/using-one-click-deploy) to try it out quickly or you can get started with the [Defang CLI](/docs/intro/getting-started). - -This page highlights architectural considerations when deploying to the Playground and any differences you might encounter when deploying to the Playground versus deploying to your own cloud account. - -:::info -The Playground allows only 1 deployed project at a time. Use the CLI `defang down` command to tear down a project before deploying a new one. -::: - -## Overview - -Overall, the Defang Playground is very similar to deploying to your own cloud account. The Playground runs on a Defang-managed AWS account, so you can expect it to work similarly to deploying to [AWS](./aws). - -### Managed services - -In essence, the Playground does not support any [managed storage](../concepts/managed-storage) services, ie. `x-defang-postgres` and `x-defang-redis` are ignored when deploying to the Playground. You can however run both Postgres and Redis as regular container services for testing purposes. - -### Managed LLMs - -Defang offers integration with managed, cloud-native large language model services with the `x-defang-llm` service extension when deploying to your own cloud account with BYOC. This extension is supported in the Defang Playground with one caveat: your MODEL (model ID) will be limited to a default model chosen by Defang. diff --git a/docs/tutorials/adding-custom-one-click-deploy.md b/docs/tutorials/adding-custom-one-click-deploy.md index 30bd9f96d1..6566f2463d 100644 --- a/docs/tutorials/adding-custom-one-click-deploy.md +++ b/docs/tutorials/adding-custom-one-click-deploy.md @@ -9,7 +9,7 @@ import { URLProvider, URLEncode } from "../../src/components/OneClick"; # Adding Custom 1-Click Deploy to Your App -This tutorial will show you how to add a 1-Click Deploy link so other people can easily deploy your app to the Defang Playground and eventually to their own cloud accounts. +This tutorial will show you how to add a 1-Click Deploy link so other people can easily deploy your app to their own cloud accounts using Defang. The link is often placed as a button in the `README.md` file of your project repository, and is the easiest way to allow anyone to deploy your app. @@ -47,7 +47,7 @@ on: jobs: deploy: - environment: playground + environment: production runs-on: ubuntu-latest permissions: contents: read diff --git a/docs/tutorials/deploy-to-playground.mdx b/docs/tutorials/deploy-to-playground.mdx deleted file mode 100644 index 8a38b2f36d..0000000000 --- a/docs/tutorials/deploy-to-playground.mdx +++ /dev/null @@ -1,69 +0,0 @@ ---- -title: Deploy to Playground -description: Deploy to the free Defang Playground. ---- - -# Deploy to Playground - -This tutorial will show you how to deploy your project to the free [Defang Playground](/docs/concepts/defang-playground). - -## Prerequisites - -- [The Defang CLI](/docs/intro/getting-started#install-the-defang-cli) -- [A Defang Account](/docs/concepts/authentication) -- [A `compose.yaml` file in your project](https://docs.docker.com/compose/gettingstarted/) -- [A Dockerfile in your project](https://docs.docker.com/get-started/docker-concepts/building-images/writing-a-dockerfile/) or use [Railpack](../concepts/railpack.md) - -## CLI - -### Step 1 - Navigate to your project directory - -Head to the folder where your project is located. - -```bash -$ cd path/to/your/project -``` - -### Step 2 - Deploy - -``` -$ defang compose up -``` - -If you have not used Defang before, you'll be prompted to log in. - -``` - ! Please log in to continue. -Please visit http://127.0.0.1:49154 and log in. (Right click the URL or press ENTER to open browser) -``` - -:::info -To learn more about how authentication works in defang, check out the [authenticating page](/docs/concepts/authentication). -::: - -When you do this, you should see something similar to the output below: - -``` - * Uploading build context for app - * Deploying service app - * Monitor your services' status in the defang portal - - https://portal.defang.dev/service/app - * Tailing logs for deployment ID o59k89vk3qc8 ; press Ctrl+C to detach: - * Press V to toggle verbose mode -2024-09-19T10:50:53.572443-07:00 cd Update started for stack jordanstephens-prod1 -2024-09-19T10:51:05.536299-07:00 cd Update succeeded in 11.99769745s ; provisioning... -2024-09-19T10:51:39.419693-07:00 app Server running at http://0.0.0.0:3000/ - * Service app is in state DEPLOYMENT_COMPLETED and will be available at: - - https://jordanstephens-app--3000.prod1.defang.dev - * Done. -``` - -You can also check on your deployment on the on the [Defang portal](#defang-portal) as well. - ---- - -## Defang Portal - -Now we can go to [https://portal.defang.dev/service/app](https://portal.defang.dev/service/app) to see our service listed in the Defang portal. - -![screenshot of the defang portal](/img/getting-started-portal.png) diff --git a/docs/tutorials/deploy-to-your-cloud.mdx b/docs/tutorials/deploy-to-your-cloud.mdx index 509ed8e449..b82c5f38ae 100644 --- a/docs/tutorials/deploy-to-your-cloud.mdx +++ b/docs/tutorials/deploy-to-your-cloud.mdx @@ -9,7 +9,6 @@ This tutorial will show you how to deploy your services to your own cloud accoun :::tip Defang makes it easier to deploy to any cloud—in your *own* cloud accounts. We refer to this as [bring-your-own-cloud (BYOC)](/docs/concepts/defang-byoc). -If you aren't ready to deploy to your own cloud account, you can use the [Defang Playground](/docs/concepts/defang-playground) to get a feel for how Defang works for free. ::: ## Choose your cloud diff --git a/docs/tutorials/deploy-using-pulumi.mdx b/docs/tutorials/deploy-using-pulumi.mdx index 7d66046453..238b127c8d 100644 --- a/docs/tutorials/deploy-using-pulumi.mdx +++ b/docs/tutorials/deploy-using-pulumi.mdx @@ -5,7 +5,7 @@ title: Deploy Using Pulumi # Deploy Using Pulumi :::warning -At the time of writing, the Defang Pulumi Provider only works with [Defang Playground](../concepts/defang-playground.md). We are working on [BYOC](../concepts/defang-byoc.md) support. +At the time of writing, the Defang Pulumi Provider does not yet support [BYOC](../concepts/defang-byoc.md). We are working on adding support. ::: This tutorial will show you how to deploy Minio with Pulumi using the Defang Provider. @@ -124,7 +124,7 @@ defang tail --name minio ### Logging Into Minio -The [Defang Playground](../concepts/defang-playground.md) will give you a domain, which you can obtain by running the following command: +Defang will give you a domain, which you can obtain by running the following command: ```bash defang ls | grep 'minio.*9001' diff --git a/docs/tutorials/deploy-with-gpu.mdx b/docs/tutorials/deploy-with-gpu.mdx index e517565398..5c77352507 100644 --- a/docs/tutorials/deploy-with-gpu.mdx +++ b/docs/tutorials/deploy-with-gpu.mdx @@ -9,7 +9,7 @@ This tutorial will show you how to create and deploy a GPU-powered application o We will walk you through the whole deployment process based on the [Mistral & vLLM](https://github.com/DefangLabs/samples/tree/main/samples/vllm) sample. :::info -Note that GPU deployments are not permitted on the Defang Playground. You must [upgrade to a paid account](https://defang.io/pricing/) and [deploy to your own cloud account](/docs/tutorials/deploy-to-your-cloud). +GPU deployments require a paid account. You must [upgrade to a paid account](https://defang.io/pricing/) and [deploy to your own cloud account](/docs/tutorials/deploy-to-your-cloud). :::