# diploi.com > Diploi is a magical developer experience platform for managing, developing, and hosting your full application. It lets you launch, test, and share environments with one click, no local installs required, no complex DevOps setup. Pick from a growing catalog of frameworks that includes Next.js, React + Vite, Astro, SvelteKit, Node.js, Django, Bun, Hono, Nue.js, Ghost, n8n, Django, Flask, FastAPI, Supabase and Laravel. Add-ons include PostgreSQL, Redis, MongoDB, MariaDB, and MinIO. You define your infrastructure in a diploi.yaml file, and Diploi spins up the entire stack automatically. Remote development is frictionless: use the browser IDE, connect via SSH, or go remote VS Code. Enjoy instant logs, GitHub integration with CI/CD, and full infrastructure-as-code. Share staging environments via link, test in live staging, push to deploy, and monitor everything in production with ease. Diploi cuts hours off development: • Up to 24× faster at starting new projects • 10× faster at onboarding new developers • 11× faster in creating test environments • 5× faster production updates Diploi saves about 300 hours per developer per year. *Complete documentation content below* # Developer, Welcome Home > Diploi is a platform that lets you build using remote development and host web apps online with one click, without configuring servers manually. Diploi is the place to develop prompt test release host develop - - - - - - - - - - - - - - - - - - - - - * * * * * * * * * * * * * * * * * * * * * [Get Started](#StackBuilder) - [- Book a Demo](https://calendly.com/hello-diploi/30min) [- GitHub](https://github.com/diploi) [- Discord](https://discord.gg/vvgQxVjC8G) 1 ## Pick Your Stack Choose from a constantly growing list of technologies to build your ideal stack. We’ll take care of configuring your monorepo. [New](/lovable) [Import from Lovable Go to import page](/lovable) ### Components Base blocks of your Stack. Include editable code. New n8n 516 \[ ] New Laravel 351 \[ ] New FastAPI 335 \[ ] New Flask 291 \[ ] New Deno 274 \[ ] New Supabase 273 \[ ] Next.js 7 841 \[ ] Node.js 3 029 \[ ] Bun 2 840 \[ ] React + Vite 1 961 \[ ] Astro 989 \[ ] SvelteKit 818 \[ ] Nue 780 \[ ] Ghost 530 \[ ] Hono 451 \[ ] Beta Django 565 \[ ] ### Add-ons Complementary services. Configurable with config. PostgreSQL 9 116 \[ ] Redis 1 450 \[ ] MongoDB 1 347 \[ ] MariaDB 1 245 \[ ] MinIO 385 \[ ] diploi.yaml ``` ``` Launch Stack Instant launch. No sign-up required. --- 2 ## Develop Your App Zero-install development environments with a single click. Edit your code directly with our powerful Browser IDE, or connect remotely with your favorite IDE. ### Effortless Development Develop remotely with Diploi using our fast browser IDE, or connect your own over SSH. - Zero-install Browser IDE ........................................... - Local VS Code remote ........................................... - SSH connection ........................................... ### Zero-Install Environments Spin up dev environments instantly, no local setup required. ### Real-Time Logging Quickly view live logs right from your browser. ### GitHub Integration Automatic Git integration with CI/CD setup. Just push it. ### Infrastructure as Code Consistent, predictable environments. Your entire infrastructure configuration will be stored in a single YAML file. ### Custom Components Add custom components to your monorepo for complete control. Kubernetes Docker ### Developer FAQ Quick answers to common developer questions. #### What is Diploi? \[ ] Diploi is a platform that combines cloud development environments and app hosting in a single place, and is meant to be an all-in-one solution where developers can scaffold applications from zero, start developing applications without a local setup using cloud development environments, which do not require any configuration work, and deploy staging and production environments instantly. All applications launched and hosted on Diploi come with a CI/CD pipeline setup by default, automatic SSL certificates, and zero-config cloud development environments. #### Where is my code stored, and how does Git integration work? \[ ] Your code lives in your own GitHub repository. Diploi configures a GitHub Action that triggers a CI/CD workflow that updates your staging and production environments, and is triggered when new updates are pushed to the repository linked to a project hosted in Diploi. #### Is there a limit to how many components or add-ons a project can have in Diploi? \[ ] There is no limit, so you can have all supported frameworks and databases supported by Diploi, the only limitation is the computing power required by a deployment to handle a large stack of components and add-ons. #### Is Diploi a VPS provider? \[ ] No, Diploi is a fully managed development and deployment platform. You cannot choose the OS where your application is deployed, and you do not have configuration access to the server's settings. #### Do I get SSH access to the servers where my project is hosted in Diploi? \[ ] Yes, Diploi uses Kubernetes to host your application's cloud development environment, components, and add-ons as individual pods, which you can access via SSH. #### Can I share my application with others for testing? \[ ] Yes, each environment has a unique URL you can share, so others can access and test your app instantly. #### How do I monitor logs or production status? \[ ] Diploi provides real-time logging for each component and add-on that is part of your application. Additionally, from the deployment's dashboard, you have access to graphs showing the resource usage of your app's cluster and its current health status. Additionally, all development deployments on Diploi come with a Diploi CLI, which gives you access to logs in real-time and can be used for programmatic log data tracking #### What if I want to move off Diploi later? \[ ] You can move your project out of Diploi at any point. All Diploi projects can be run on any VPS or managed hosting service, either by running each component and add-on as you usually would do via terminal commands (eg. npm run start), or by using the Dockerfiles that Diploi generates for your app's components. #### Is there a free trial or credits? \[ ] When you sign up with GitHub, you receive €50 in free credits valid for 14 days. These credits let you explore Diploi fully without a credit card. After the trial, you only pay for the time that your application is online and the storage utilized. There are no additional costs or fees for extra services. #### What is the Stack Builder in Diploi? \[ ] Stack Builder is a tool for scaffolding new apps. It can generate boilerplate code and project structure for common stacks. For example, you can pick frameworks and databases, and the Stack Builder will create a ready-to-launch application template. This jumpstarts new projects so you can begin coding immediately. --- 3 ## Publish Your App We take care of the full lifecycle of your app. You can spin up any kind of environment with a single click. ### Test Environments Create staging environments to test your application with a single click. ### Share With Link Share access to environments with a web link and invite anyone to test. ### CI/CD Automatically configured GitHub actions for easy CI/CD pipelines. ### Push to Deploy Automatically update environments with a push, including infrastructure. ### Monitor Production Single-click access to logs. Easy to read status trees for environment services. --- ## Benefits of Diploi These are real-life statistics from a web development company. Can you afford to ignore the benefits and savings from Diploi? ### Consistent - Consistent environments from development to production - Straightforward yet powerful user experience - Adoptable incrementally - start easy, grow later ### One-Click - Fast 30 second new developer onboarding - One-click environment setup - Instantly shareable testing environments ### Zero-Install - Zero-install remote development - Versatile support for any stack pre-build or custom ### This means, that on average, Diploi saves300hfor every developer, every year. ### [Diploi for Developers](/features/dev) [Zero-install cloud development](/features/dev) ### [Diploi for Teams](/features/teams) [Ship faster with zero-config](/features/teams) ### [Diploi for DevOps](/features/devops) [GitOps & push to deploy](/features/devops) ### [Diploi for Vibes & AI](/features/ai) [From vibes to prod with zero-config](/features/ai) ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) ## Contact Us If you're considering our Pro or Enterprise tiers, feel free to reach out to us directly. We're here to answer your questions and assist with upgrading your account. [Book a Demo](https://calendly.com/hello-diploi/30min) --- # Diploi as an Alternative to Railway > Diploi compared with Railway, in this article we explore the differences between both platforms and their strengths. Javier November 24, 2025 Let’s explore how the two platforms overlap and what might be unique to each. Both target freelancers, agencies, and startups looking to simplify deployment and development workflows. ## Table of contents - [TLDR](#tldr) - [Who is it for?](#who-is-it-for) - [Feature comparison](#feature-comparison) - [Pricing comparison](#pricing-comparison) - [When to choose Diploi instead of Railway](#when-to-choose-diploi-instead-of-railway) - [FAQ](#faq) - [Considering migrating from Railway to Diploi?](#considering-migrating-from-railway-to-diploi) - [References](#references) ## TLDR - **Railway provides** a fully managed, Git-driven infrastructure platform that scales containerized services with minimal setup. - **Diploi provides** fully managed hosting and integrated cloud development environments, with no setup required to start new applications from zero and deploy online. - **Pick Diploi** when you want a ready-to-code cloud development workspace, instant app scaffolding, which is online right from the start. Ideal for rapid prototyping, hackathons, working on multiple projects without custom local setups, team collaboration, or fast onboarding for new team members and contractors. - **Pick Railway** when you prefer a traditional Git-driven deployment model with per-service control, integrated managed databases and queues, and fine-grained scaling. Diploi targets ease-of-use and speed, with remote IDEs and one-click deployment environments, while Railway offers a developer-friendly deployment platform similar to Render with broad flexibility and control. ## Who is it for? Both Railway and Diploi target developers, freelancers, agencies, and startups who want to focus on code rather than managing servers individually. **Railway** is aimed at teams that need a straightforward hosting solution. It lets you provision infrastructure, where you develop locally, and when your project is ready, you can upload it to Railway by importing from GitHub, using the CLI, or by uploading a Docker Image. Railway’s tiered plans (including a free tier and $5/month hobby plan) make it accessible to solo developers, while paid plans ($20 Pro) add features like priority support and global regions. It’s a good fit if your project has multiple services (web frontends, APIs, workers, databases) and you want each as a separate deployable service. **Diploi**, on the other hand, is meant for developers and teams that want to eliminate local setup entirely, to reduce context switching complexity. It not only abstracts infrastructure but also provides ready-to-use application scaffolds and built-in remote development environments. Every new Diploi project starts with a remote dev environment, which can be accessed with a built-in browser IDE or from any IDE using SSH, so developers and contractors can start coding immediately without npm installs or config. ## Feature comparison Feature | Diploi | Railway Deployment model | You create one environment that hosts all services and databases together in a single Kubernetes cluster. This monolithic setup is designed to reduce overhead and costs. | You create separate services for each component (frontend, backend, API, worker, database, etc.). Each service is its own instance on Railway’s platform. CI/CD automation | Diploi creates a GitHub Action that, when you push to your GitHub repo, rebuilds your app’s container images and updates the live deployment when the build succeeds. | Railway automatically redeploys on Git commits for connected services. You link a GitHub repo, and Railway will build and deploy on each push. Using the CLI, is it possible to create custom CI/CD workflows. Managed services | Diploi provides managed databases as part of any project hosted, but there isn’t a separate catalog of managed services like cron jobs, edge functions, workers, etc. In Diploi, these services can be run within a project by adding components to run these services, eg, using Bun to run cron jobs. | Railway offers a catalog of managed open-source databases (Postgres, MySQL, Redis, Mongo, etc.) and volume storage, all with built-in backups. It also supports running background jobs by scheduling a service with a cron trigger. Development experience | Includes a built-in cloud development environment. Every Diploi project starts with a ready IDE (in-browser or via VS Code/Cursor/SSH), so developers can code without any local setup. Onboarding is much faster since developers do not need to configure their local environment for every project they will work on. | Railway does not support cloud development environments, but the deployment workflow is unintrusive and flexible for developers, by supporting GitHub and Docker Images as a way to update services. ## Pricing comparison Diploi has a usage-based pricing model, and it depends on the size of the cluster your application uses, regardless of how many components and add-ons are hosted within the same cluster. You can have unlimited collaborators in a project, and use any amount of resources as you need, while only getting charged for the time that your deployments are online and the storage they require. Railway is also priced based on usage, but with a minimum charge based on the tier plan you choose. Depending on the tier you choose, you can unlock computing, networking, and storage resources, along with increased team seats to collaborate on projects. For a project, hosting a web application that uses FastAPI for the backend, Astro for the frontend and Postgres as the database, that uses 10gb of storage, a 2-core CPU, and 4gb ram minimum: - Diploi, **€19.5/month**. - Railway, requires a Pro subscription, which costs **$20/month** or in Euros, **\~€17.32/month**. ## When to choose Diploi instead of Railway Choose **Diploi** when you want smooth context switching between projects and if you work on multiple projects built with different frameworks and databases. For example, if you want a one-click staging-to-production pipeline and a ready-made workspace you can hand to a freelancer or colleague without any setup, then Diploi is the way to go. Using cloud development environments means that you can start coding immediately, and then deploy online instantly without having to configure servers or SSL certificates, as Diploi takes care of all the infrastructure configuration automatically. Choose **Railway** when your team prefers a service-per-container architecture and more granular DevOps control over each service’s computing resources. Railway is ideal if you have an existing codebase and want to deploy each microservice or database as its own unit, possibly with Docker, CLI, or from GitHub. It also offers the ability to scale services within an application independently for more control over the performance of your app’s infrastructure. ## FAQ ### Can I connect existing databases? **Diploi:** Yes. Diploi lets you add managed databases through its stack add-ons or by attaching external database instances to your components by adding credentials in your project’s environment variables. **Railway:** Yes. Railway allows you to provision built-in databases (Postgres, MySQL, etc.) as services, and you can also connect to external databases via environment variables. ### Does Diploi support background workers similar to Railway? Yes, but not as a standalone service. In a Diploi project, you can create background workers within your app’s stack by adding a dedicated component to run jobs, like Hono, Bun, Deno, or FastAPI. This way, you can have background job workers or cron processes where needed, but without extra charges since the jobs are running within the same cluster. ### How does scaling compare? Diploi handles scaling by using predefined cluster sizes. You pick a cluster (S, M, L, XL) and it runs at that size, and switching sizes is how you scale your app. Railway supports both vertical autoscaling (each service can scale up to the plan’s CPU/RAM limits) and manual horizontal scaling (by adding more replicas of a service). ### Can I use both platforms? Yes. Nothing prevents you from mixing platforms. For instance, you could develop in Diploi’s remote environment and deploy some services on Railway, or vice versa. Both platforms use standard networking, so you could even connect a Railway-managed database to an app on Diploi or have services on one platform talk to services on the other. ## Considering migrating from Railway to Diploi? If you’re using Railway but want to try Diploi (or migrate), we’d be happy to assist. You can reach out via our support channels (email or Discord) or book a demo to discuss migration steps and best practices. ## References - [Diploi docs](https://docs.diploi.com) - [Railway homepage](https://render.com/) - [Railway docs](https://docs.railway.com) --- # Diploi as an Alternative to Render > Diploi is an alternative to Render, in this article we compare both in terms of their ease of use, remote development capabilities, deployment workflow, user experience, and pricing. Javier November 24, 2025 This article provides a comparison between the features of Render and Diploi to explain how both platforms overlap and what features might be unique to each. Let’s get started! ## Table of contents - [TLDR](#tldr) - [Who is it for?](#who-is-it-for) - [Feature comparison](#feature-comparison) - [Pricing comparison](#pricing-comparison) - [When to choose Diploi instead of Render](#when-to-choose-diploi-instead-of-render) - [FAQ](#faq) - [Considering migrating from Render to Diploi?](#considering-migrating-from-render-to-diploi) - [References](#references) ## TLDR - **Render provides** fully managed infrastructure for services with Git-driven deploys. - **Diploi provides** fully managed hosting and remote development environments within one platform. - **Pick Diploi** when you want to skip all the need for DevOps, you can start from zero with a ready scaffold environment, which is online from the start and allows you to start coding, or by importing from GitHub. - **Pick Render** when you have a project already developed and if you need control over the infrastructure and networking. In short, Diploi targets convenience for full-stack projects by providing a remote development environment and one-click hosting, while Render provides a more traditional cloud hosting approach with fine-grained control over each service. ## Who is it for? Both platforms target a similar audience, developers, teams, and freelancers who want to abstract how their applications are hosted online, while avoiding the chore of managing servers. Render is for developers and teams who need a cloud hosting solution for production applications. You can choose to deploy web services, APIs, background workers, static sites, and databases. Render is a good fit if you require more scalability or separation of concerns, for example, running multiple microservices, dedicated background job workers, or scheduling cron tasks. With Diploi, developers and teams not only abstract their infrastructure, but also can generate app scaffolds that they can start developing right away, without ever having to run an npm command. While it is intended mainly for production workflows, Diploi excels at quick prototyping tasks, hackathons, or projects where you need to go from code to cloud quickly, because all Diploi projects start with a remote development environment, which can be accessed via a browser-based IDE, VS Code, Cursor, and any other IDE that supports SSH connections. ## Feature comparison Feature | Diploi | Render Deployment model | You create one environment that hosts all services and databases within a single Kubernetes cluster to reduce costs and complexity. | You create separate services for each component (web app, worker, database, etc.). Each service runs in its own container/instance on Render’s cloud. CI/CD automation | Creates a GitHub action in your repository that rebuilds your app’s images and updates deployments when builds are successful. | Updates deployed services on push, based on Git branches and auto-scaling rules. Managed services | Offers managed databases linked to components, and it doesn’t have separate managed services, but it facilitates how you can build services like cron jobs, background workers, and edge functions, by running them as part of a monorepo environment to host all services within a cluster. | Offers a dedicated catalog of managed databases, queues, cron jobs, and background processes. Development experience | Offers a built-in cloud development environment with the option to connect your local VS Code or Cursor, via SSH. It greatly simplifies onboarding new developers (they can start coding without installing anything) and ensures “it works on my machine” is the same as the server. | No integrated dev environment. Render does not provide an in-browser IDE or development environment, it focuses purely on hosting. Developers typically develop locally (or use their own codespaces) and then deploy to Render via Git push or Docker. Render will automatically build and deploy new commits (CI/CD), but you need to manage your code editor/environment separately. ## Pricing comparison Diploi pricing depends on the size of the cluster you use per deployment and the amount of storage utilized. Render prices each service independently (web services, background workers, databases, and cron jobs). For a project, hosting a web application that uses FastAPI for the backend, Astro for the frontend and Postgres as database, which requires 10gb of storage, and 4gb ram minimum: - Diploi, **€19.5/month**. - Render, €21.5 for FastAPI + €21.5 for Astro + €16.4 for Postgres, in total **€59.4/month**. ## When to choose Diploi instead of Render Choose Diploi when you need remote development environments, a predictable staging-to-production workflow, and a workspace you can hand to contractors without setup time. Choose Render when your team prefers to control service composition, wants managed data stores in the same provider, or already runs Git-based deploys with Docker images. ## FAQ ### Can I connect existing databases? Yes. You can provision databases through the Diploi stack template or connect external instances by adding credentials to the project settings. ### Does Diploi support background workers similar to Render? Diploi templates include background job workers where the stack requires them, and you can add custom processes when forking a template. ### How does scaling compare? Diploi automates scaling through predefined stack sizes. Render offers per-service scaling controls and auto-scaling policies. ### Can I use both platforms? Yes. You can keep Render services live and connect them to applications hosted on Diploi. ## Considering migrating from Render to Diploi? We would be more than happy to assist you. You can reach out to our team via email, Discord or scheduling a call with our team. ## References - [Sign up for Diploi](https://console.diploi.com) - [Browse the Diploi docs](https://docs.diploi.com) - [Render homepage](https://render.com/) - [Render Docs](https://render.com/docs) --- # Diploi as an Alternative to Vercel > Diploi vs Vercel, a deep-dive into how both platforms compare. Javier November 24, 2025 In this article we explore a comparison between the features of **Vercel** and **Diploi**, to explain how both platforms overlap and what features are unique to each. ## Table of contents - [TLDR](#tldr) - [Who is it for?](#who-is-it-for) - [Feature comparison](#feature-comparison) - [Pricing comparison](#pricing-comparison) - [When to choose Diploi instead of Vercel](#when-to-choose-diploi-instead-of-vercel) - [FAQ](#faq) - [Considering migrating from Vercel to Diploi?](#considering-migrating-from-vercel-to-diploi) - [References](#references) ## TLDR - **Vercel** is a hosting platform designed for front-end and static site hosting with zero-config deployment. It provides a Git-driven CI/CD workflow, with global edge caching and flat-fee pricing with additional fees for advanced logs and cloud function invocations. - **Diploi** offers an all-in-one full-stack platform, where every project starts with a cloud IDE and with exposed endpoints online by default. Diploi has a usage-based pricing, with no additional fees. It automates deployments, manages databases, and provides a cloud development environment to allow coding from the browser or to connect VS Code, Cursor, and other SSH-capable IDEs to code without a local setup. - **Pick Diploi** if you need predictable pricing by paying only for the time that your deployments are online, and you are working on full-stack apps. It’s ideal for freelancers and teams that need fast deployment workflows without spending time configuring servers, and manage multiple fullstack projects at the same time, which use different tech stacks. Diploi provides a cloud development environment for projects, which simplifies context switching between projects, as devs do not need to manage different local environments on their local machine. - **Pick Vercel** if you are deploying primarily frontend or Next.js apps, and need an edge/CDN platform that abstracts the infrastructure layer and provides a smooth deployment workflow. Vercel provides additional developer-friendly features like push-to-deploy with previews, which allows devs to generate preview environments for pull-requests, and is well-suited for static sites or frontend projects with large traffic volumes. In short, Diploi targets convenience and predictability for full-stack projects by combining development and hosting into one platform, while Vercel focuses on effortless deployment and global delivery for modern web frontends. ## Who is it for? At its core, both platforms help developers, freelancers, agencies, and startups who want to build web apps without managing servers manually, but they solve different problems. - **Vercel** is **ideal for front-end projects**. If your app is built with Next.js, React, Vue/Nuxt, Svelte, or similar frameworks, Vercel provides zero-config builds and a global CDN out of the box. Teams using Vercel can deploy via GitHub or GitLab and get instant preview deployments for every pull request. It’s a great fit when you need high-scalability static or serverless sites. Vercel’s Hobby tier is free for personal projects, and the Pro tier ($20+/mo) adds higher quotas and collaboration features. - **Diploi** is **geared towards full-stack development**, but it can also be used to host front-end only applications, with global CDN coverage for static sites. It provides a **cloud development environment** for every project, which can be accessed from Diploi’s browser IDE or from any IDE with support for SSH-remote access like VS Code or Cursor, which means that developers can start coding immediately without requiring a local setup. Diploi only charges for the time that deployments are online and the storage they use, without any other charges. ## Feature comparison Feature | Diploi | Vercel Deployment model | A single multi-service environment per project. All components (frontend, backend, databases, workers) run together in one Kubernetes cluster. | Each deployment is independent (containerless). Static sites and serverless functions are deployed separately. There’s no unified environment. GitOps / CI/CD | Deep GitHub integration. Diploi generates a GitHub Action for your repo that rebuilds and deploys your app on each commit. It also supports preview URLs and automatic SSL certificate generation. | Instant git-driven deployments. Vercel auto-builds and deploys on every branch push, providing preview URLs for pull requests. Merging to the production branch triggers a live deployment. No manual pipelines are needed. Managed services | Built-in managed databases (eg, Postgres) and key services as part of the same environment. Background jobs or cron tasks can be run in the same cluster by adding a component to handle them separately. | No native DB or full-stack services supported. Vercel focuses on frontends and function invocations. Any database or cache used must be supplied externally (eg, using a DB provider from Vercel’s marketplace). There are no built-in managed databases or message queues. Development experience | Fully integrated cloud IDE. Developers can code in the browser or connect via SSH (VS Code, Cursor, etc.). | No built-in IDE. Development is local or via another cloud editor like GitHub Codespaces. Vercel’s strength is not IDEs but rapid deploys. However, its workflow (push-to-deploy with instant previews) offers a smooth experience for frontend-focused devs. Performance and scaling | Environments are always hot, without cold starts. You choose a cluster size (S/M/L/XL), and it runs continuously. Scaling can be done vertically, by selecting a larger cluster. Diploi comes with a global CDN to improve the performance of static content delivery. | Environments with low traffic can have latency due to cold-starts in the free plan, but for Pro and higher tiers, there’s minimal latency due to cold-starts. Vercel functions and frontend apps auto-scale based on traffic, and scale to zero when idle. Vercel includes a global CDN for fast static delivery. ## Pricing comparison Diploi is purely usage-based, only charging for the time deployments are online and the storage they use. There are no other charges for data traffic, team seats or monitoring. It does not have a free or hobby plan, but it offers a 14-day trial to get started on the platform. For example, a **production** environment with a small cluster (2 vCPU, 4GB RAM) running 24/7 costs about **€19/month**. Development environments (used only 7h/day) can average as low as **€4/month**. There are no additional service fees, just compute hours and storage. Vercel has a free hobby plan, with fair usage clauses, and for its paid services, it uses a hybrid model with a fixed base fee, plus usage overages (bandwidth, function invocations, build minutes) and additional services like improved observability metrics and logs. The **Pro plan** is $20/month (**\~€17.32/month**), which includes $20 in usage credits, up to 1 TB of free bandwidth per month. Beyond that, you pay **overages**: e.g. $0.15 per GB of extra bandwidth, $2 per million function invocations, $10 for advanced observability features, etc. Because Vercel metering is granular, actual bills can be hard to predict. In contrast, Diploi’s straightforward hourly billing makes costs predictable, especially for projects that have a large volume of traffic. ## When to choose Diploi instead of Vercel **You want an all-in-one workflow with no DevOps**, which is why Diploi provides a cloud IDE and allows quick app scaffolding, so developers can start coding immediately. You won’t need to manage separate hosting for the frontend, backend, and database, as they all run together. As for costs, Diploi has predictable, usage-based pricing, where you only pay for the time your app is running. There are no unexpected charges for extra services or traffic. **You are developing Full-stack applications**, where you need a persistent database and a dedicated backend, and Diploi’s unified environments make deployment simpler while minimizing costs by hosting all parts of your app within a single cluster. **Contractor-friendly and fast onboarding for teams**, so you can add new team members to projects without any additional costs, and get them coding in the same environment without any time spent setting up locally or worrying about dependencies. This is convenient for agencies working with remote developers. In summary, pick Diploi when convenience and cost predictability are important. It’s the better choice if you need an instant development workspace plus production hosting, with **no surprise bills**. ## FAQ ### Can I host frontend-only apps on Diploi? Yes, in Diploi, you can start a frontend app using Next.js, React+Vite, SvelteKit, and Astro, plus you can import from GitHub and Lovable. ### Does Diploi support background jobs or cron tasks? Diploi projects can have worker processes or scheduled jobs as part of the same environment by running a component within the same cluster to handle these tasks. Unlike Vercel (which has serverless Functions and separate Cron Jobs), Diploi can run background tasks using a task runner container using Bun, Deno or FastAPI. The effect is similar, you can perform periodic or asynchronous work, but it’s managed within your single project environment and without additional costs. ### How does autoscaling work? Diploi uses cluster size (S, M, L, XL) and scaling means upgrading to a larger size. Vercel, by contrast, auto-scales **serverless functions** up and down based on traffic. On the Pro plan Vercel uses Fluid Servers to warm up functions (so you get effectively zero cold starts and can support many concurrent executions). ### Can I use both platforms together? Yes. For example, you could host your frontend or static assets on Vercel and have Diploi host your API/backend. They can interoperate over the web (via custom domains or API calls). ## Considering migrating from Vercel to Diploi? If you’re exploring a switch or want to add Diploi to your workflow, we’re happy to help. Diploi’s team offers migration assistance, documentation, and a community (Discord, email, etc.) to guide you. We can help port your projects and ensure everything runs smoothly. **Get in touch** if you’d like support with migrating or integrating with Diploi. Our goal is to make it seamless. ## References - [Sign up for Diploi](https://console.diploi.com) - [Diploi docs](https://docs.diploi.com) - [Vercel homepage](https://vercel.com/) - [Vercel Docs](https://vercel.com/docs) --- # Blog > Tutorials, insights and case studies about building and deploying modern apps with remote development and one-click deployment workflows. ## See what the team has been up to ### [Using Cursor with apps built with Lovable, and hosting without Lovable Cloud](/blog/importing_from_lovable) [Import and deploy Lovable AI apps directly from your GitHub account or public repositories and code with Cursor](/blog/importing_from_lovable) [- Guide- October 17, 2025](/blog/importing_from_lovable) --- ### [Importing Lovable apps and more from an existing Repository to Diploi](/blog/importing_from_lovable_and_github) [You can now import apps directly from your GitHub account or public repositories, and host them instantly on Diploi](/blog/importing_from_lovable_and_github) [- Guide- September 26, 2025](/blog/importing_from_lovable_and_github) --- ### [Supabase on Diploi](/blog/hosting_supabase) [How to get started with Supabase, using Diploi to host a project.](/blog/hosting_supabase) [- Guide- September 25, 2025](/blog/hosting_supabase) --- ### [Hosting n8n on Diploi](/blog/hosting_n8n) [Spin up n8n: Build automations, preview, and ship without DevOps.](/blog/hosting_n8n) [- Guide- September 23, 2025](/blog/hosting_n8n) --- ### [FastAPI on Diploi: Code, preview, and ship without DevOps](/blog/hosting_fastapi_apps) [Start a FastAPI service with remote development, live previews, and one-click production, without configuring SSL certificates or manual server config.](/blog/hosting_fastapi_apps) [- Guide- September 22, 2025](/blog/hosting_fastapi_apps) ### [Deploying Flask Apps the Easy Way](/blog/hosting_flask_apps) [Use Diploi to run and iterate on Flask without touching servers](/blog/hosting_flask_apps) [- Guide- September 22, 2025](/blog/hosting_flask_apps) ### [How to create Laravel apps that are ready for Production using Diploi](/blog/hosting_laravel_apps) [In this tutorial guide we go over the process of creating and hosting an application using Laravel in Diploi](/blog/hosting_laravel_apps) [- Guide- September 22, 2025](/blog/hosting_laravel_apps) ### [Deploying Deno Applications in Easy Mode](/blog/hosting_deno_apps) [How to use Diploi to host and develop Deno-powered apps without configuring servers](/blog/hosting_deno_apps) [- Guide- September 22, 2025](/blog/hosting_deno_apps) ### [Exploring 7 Lesser Known AI Coding Extensions for VS Code](/blog/exploring-7-lesser-known-ai-coding-extensions) [In this article, we check interesting AI coding alternatives to the popular AI coding tools in the Visual Studio Marketplace](/blog/exploring-7-lesser-known-ai-coding-extensions) [- Blog- September 18, 2025](/blog/exploring-7-lesser-known-ai-coding-extensions) ### [Hosting a Ghost blog in seconds on Diploi, with support for custom development](/blog/hosting_a_ghost_blog) [Learn how to create blogs and websites with Ghost using Diploi](/blog/hosting_a_ghost_blog) [- Guide- August 27, 2025](/blog/hosting_a_ghost_blog) ### [Create Astro apps quickly, from Development to Production on Diploi](/blog/hosting_astro_apps) [Bring the versatility of platforms like Heroku to your Astro development workflow](/blog/hosting_astro_apps) [- Guide- August 26, 2025](/blog/hosting_astro_apps) ### [Starting a new Bun app on Diploi](/blog/hosting_bun_apps) [Explore how to create new Bun applications readily online, without any server config](/blog/hosting_bun_apps) [- Guide- August 25, 2025](/blog/hosting_bun_apps) ### [The best way to start new Django apps and host them online](/blog/hosting_django_apps) [Use Django on Diploi to skip server config and focus only on the code, no DevOps](/blog/hosting_django_apps) [- Guide- August 24, 2025](/blog/hosting_django_apps) ### [How to create Hono apps that are ready for Production using Diploi](/blog/hosting_hono_apps) [Make your Hono development as seamless as deploying on Heroku](/blog/hosting_hono_apps) [- Guide- August 23, 2025](/blog/hosting_hono_apps) ### [Creating ready-for-Production Next.js apps using Diploi](/blog/hosting_nextjs_apps) [Launching Next.js faster than using Vercel and with support for monorepo apps](/blog/hosting_nextjs_apps) [- Guide- August 22, 2025](/blog/hosting_nextjs_apps) ### [Launching a new Node app? How to do it, without configuring a server](/blog/hosting_node_apps) [Build your next Node.js app with Diploi and have it live right away](/blog/hosting_node_apps) [- Guide- August 21, 2025](/blog/hosting_node_apps) ### [Start new apps with Nuejs quickly on Diploi](/blog/hosting_nuejs_apps) [Learn how to create new Nuejs apps easily and host them online without struggling with server config](/blog/hosting_nuejs_apps) [- Guide- August 20, 2025](/blog/hosting_nuejs_apps) ### [Ship new React apps using Diploi and skip the server config](/blog/hosting_react_apps) [Create your next React app using Diploi to skip any DevOps work and focus only on the code](/blog/hosting_react_apps) [- Guide- August 19, 2025](/blog/hosting_react_apps) ### [Launching SvelteKit apps, from Development to Production using Diploi](/blog/hosting_svelte_apps) [With the convenience of Vercel and the flexibility of Replit, all in a single platform, to create SvelteKit-powered apps super fast](/blog/hosting_svelte_apps) [- Guide- August 18, 2025](/blog/hosting_svelte_apps) ### [The easiest way to start new Django and Hono apps, literally one click](/blog/hono_and_django_support) [Discover how to spin up apps in seconds using Diploi with Hono and Django](/blog/hono_and_django_support) [- News- June 26, 2025](/blog/hono_and_django_support) ### [7 Remote Development Platforms in 2025, to Code without a Local Setup](/blog/remote_development_platforms) [We discuss 7 remote development platforms that you can use in 2025 to code, run, and test applications in the cloud without the need for a local setup](/blog/remote_development_platforms) [- Blog- June 10, 2025](/blog/remote_development_platforms) ### [Skip the YAML and Server Configs: 7 Easy Deployment Platforms You Haven’t Tried](/blog/deployment-platforms) [We created a list of deployment platforms (us included) that you should check out to make your development workflow faster](/blog/deployment-platforms) [- Blog- May 27, 2025](/blog/deployment-platforms) ### [Remote Development Environments with Cursor?](/blog/remote-development-with-cursor-4okl) [Now you can connect to your remote development environments on Diploi using Cursor ...](/blog/remote-development-with-cursor-4okl) [- Blog- May 6, 2025- Dev.to](/blog/remote-development-with-cursor-4okl) ### [Setting up an application with Nue.js](/blog/setting-up-an-application-with-nuejs-3261) [This is a tutorial, walking through how to set your app with Nue.js By the end of this...](/blog/setting-up-an-application-with-nuejs-3261) [- Blog- April 25, 2025- Dev.to](/blog/setting-up-an-application-with-nuejs-3261) ### [Nue.js, SvelteKit and MariaDB now available on Diploi 🎉](/blog/nuejs-sveltekit-and-mariadb-now-available-on-diploi-c5c) [We are happy to announce the new technologies that you can start deploying and develop...](/blog/nuejs-sveltekit-and-mariadb-now-available-on-diploi-c5c) [- Blog- April 14, 2025- Dev.to](/blog/nuejs-sveltekit-and-mariadb-now-available-on-diploi-c5c) ### [How to create dynamic GitHub Actions based on the contents of a repository](/blog/how-to-create-dynamic-github-actions-based-on-the-contents-of-a-repository-50j8) [If you are here, you probably know what GitHub Actions are and understand the basics of...](/blog/how-to-create-dynamic-github-actions-based-on-the-contents-of-a-repository-50j8) [- Blog- April 2, 2025- Dev.to](/blog/how-to-create-dynamic-github-actions-based-on-the-contents-of-a-repository-50j8) ### [Why we don't use an ORM and why you (probably) shouldn't](/blog/why-we-dont-use-an-orm-and-why-you-probably-shouldnt-4cfo) [Jump to TLDR? \> This post is mainly intended for coders early in their careers, ✨vibe...](/blog/why-we-dont-use-an-orm-and-why-you-probably-shouldnt-4cfo) [- Blog- March 26, 2025- Dev.to](/blog/why-we-dont-use-an-orm-and-why-you-probably-shouldnt-4cfo) ### [Easily Create Complex Stacks in Just a Few Clicks — New Release!](/blog/easily-create-complex-stacks-in-just-a-few-clicks-new-release-3gdl) [Previously, we wrote about our IaC implementation, and today we are proud to announce its public...](/blog/easily-create-complex-stacks-in-just-a-few-clicks-new-release-3gdl) [- Blog- March 17, 2025- Dev.to](/blog/easily-create-complex-stacks-in-just-a-few-clicks-new-release-3gdl) ### [A Year In Review](/blog/year-in-review) [As we reflect on the journey we've taken this year, it’s clear that 2024 has been an incredible one for Diploi.](/blog/year-in-review) [- Blog- December 30, 2024](/blog/year-in-review) ### [How We Solved Infrastructure as Code](/blog/how-we-solved-infrastructure-as-code-2ldn) [Infrastructure as Code (or IaC for short) has been gaining traction recently—and for good reason. It...](/blog/how-we-solved-infrastructure-as-code-2ldn) [- Blog- December 3, 2024- Dev.to](/blog/how-we-solved-infrastructure-as-code-2ldn) ### [Diploi Stack Builder](/blog/diploi-stack-builder-32n4) [In our previous blog post we opened up our future plans in the form of a roadmap. We also promised to...](/blog/diploi-stack-builder-32n4) [- Blog- November 6, 2024- Dev.to](/blog/diploi-stack-builder-32n4) ### [🗺️ Diploi Roadmap for 2024](/blog/diploi-roadmap-for-2024-1nde) [We’ve been hard at work building Diploi, and now that we got funded 🎉, the pace is only going to...](/blog/diploi-roadmap-for-2024-1nde) [- Blog- October 3, 2024- Dev.to](/blog/diploi-roadmap-for-2024-1nde) ### [Diploi Receives Pre-Seed Funding](/blog/diploi-received-pre-seed-funding) [Diploi has completed its first pre-seed funding round. Founded in 2024 with the ultimate goal of taking away the pain of software development by letting developers focus on their main task - to develop new and better software.](/blog/diploi-received-pre-seed-funding) [- News- September 27, 2024](/blog/diploi-received-pre-seed-funding) ### [Diploi Changelog: Browser IDE & Quick Trials](/blog/diploi-changelog-browser-ide-quick-trials-1n1c) [Hi everyone, we've been quiet here for a month, but not idle. First, a Big thank you 🙏 to everyone...](/blog/diploi-changelog-browser-ide-quick-trials-1n1c) [- Blog- April 3, 2024- Dev.to](/blog/diploi-changelog-browser-ide-quick-trials-1n1c) ### [Astro with PostgreSQL](/blog/astro-with-postgresql-1mpf) [Astro is a simple yet powerful front-end framework for content-driven websites. The common way of...](/blog/astro-with-postgresql-1mpf) [- Blog- February 27, 2024- Dev.to](/blog/astro-with-postgresql-1mpf) ### [Hi from Diploi 🎉](/blog/hi-from-diploi-52j9) [Welcome to the very first post about Diploi. We're on a journey to make software development feel...](/blog/hi-from-diploi-52j9) [- Blog- February 7, 2024- Dev.to](/blog/hi-from-diploi-52j9) ### [Diploi for Developers](/features/dev) [Zero-install cloud development](/features/dev) ### [Diploi for Teams](/features/teams) [Ship faster with zero-config](/features/teams) ### [Diploi for DevOps](/features/devops) [GitOps & push to deploy](/features/devops) ### [Diploi for Vibes & AI](/features/ai) [From vibes to prod with zero-config](/features/ai) ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) ## Contact Us If you're considering our Pro or Enterprise tiers, feel free to reach out to us directly. We're here to answer your questions and assist with upgrading your account. [Book a Demo](https://calendly.com/hello-diploi/30min) --- # Astro with PostgreSQL > Astro is a simple yet powerful front-end framework for content-driven websites. The common way of... Tuomas February 27, 2024 [Read on Dev.to](https://dev.to/diploi/astro-with-postgresql-1mpf) [Astro](https://astro.build/) is a simple yet powerful front-end framework for content-driven websites. The common way of building websites with Astro involves getting dynamic data from an external CMS or API. If you do not need a fully fledged CMS, but would still like to dynamically change some content on your Astro site, all you might need is a PostgreSQL database. ## Getting Started I will be using [Diploi](https://diploi.com/) to bootstrap this project. Diploi comes with an Astro project and PostgreSQL DB pre-configured, so no setup required. Simply choose the "Astro" template when creating a new project. You can also follow the manual installation guide on the official Astro documentation. It can be found here: . In both cases, you will get an example project with a single demo page. We will continue from there. ## Connecting to a PostgreSQL DB Let's get our Astro page to talk with PostgreSQL. First thing we need to do is to install the [node-postgres](https://www.npmjs.com/package/pg) (or "pg" for short) library from NPM. We will use this client to query our PostgreSQL DB. ``` npm i pg npm i --save-dev @types/pg ``` If you do not plan on using TypeScript, you can leave out the `@types/pg` package. The Diploi Astro template comes with an optional PostgreSQL database, with ENV variables pre-configured. If you are not using Diploi, you may specify different ENV variables, or handle the configuration is some other way. Here are the ENV variables Diploi gives us by default: ``` POSTGRES_HOST POSTGRES_PORT POSTGRES_DB POSTGRES_USER POSTGRES_PASSWORD ``` Create a `db.ts` file in the `/src` folder: ``` import pg from 'pg'; // Make sure we DO NOT "prerender" this function to allow the ENV variables to update on the fly export const prerender = false; const client = new pg.Client({ host: import.meta.env.POSTGRES_HOST, port: import.meta.env.POSTGRES_PORT, database: import.meta.env.POSTGRES_DB, user: import.meta.env.POSTGRES_USER, password: import.meta.env.POSTGRES_PASSWORD, }); await client.connect() export { client as db }; ``` This file will initialize our DB client, so we can use it in any Astro component! Let's create an example component that queries the current time from the DB. Create a `DB.astro` file in the `/src/components` directory: ``` --- import { db } from '../db'; const { rows } = await db.query('SELECT NOW() as "time"'); --- ``` This component will connect to the PotsgreSQL DB, query the current time with `NOW()`, and finally render it on the page! Try it out by adding it to the `/src/pages/index.astro` page. At the top, import the component with: ``` import DB from '../components/DB.astro'; ``` And then include it anywhere on the page with: ``` ``` Wherever you placed you component, you should see a timestamp that updates on each page load! ### That's It? You can see how simple it is to talk to the DB directly, no HTTP API needed! This way you could use your PostgreSQL DB as a simple CMS, or just have some information easily changeable without code changes. This data is not as dynamic as it may seem though. In development mode, Astro will query this data every time the page is loaded. In production, however, Astro will create a static build that will not query the DB on every page load. It only queries it once when the production build is made. If you do need the data to be updated dynamically, you can do so by enabling the fairly new SSR support in Astro. ## Enabling SSR in Astro SSR, or server-side rendering, means on-demand rendering on the server when a page is requested. This means that Astro will not build a static HTML version of your entire site, but acts more like a PHP server that builds the page on-demand when a user visits it. On Diploi, the only change you have to make is a single line in your `index.astro` page: ``` export const prerender = false; ``` By exporting this line right after any `import` statements, we tell Astro to opt this page out of static rendering, and to render it on demand whenever a client requests it. If you are not using Diploi, you will have to configure an SSR adapter for your Astro project. You will find a guide to do so in the official Astro documentation at .. ## Diploi? I have mentioned [Diploi](https://diploi.com/) quite a few times in this blog post. Diploi is a single SaaS service for managing, developing and hosting your full application. We have been building Diploi for a while now, and would love for you to have a go (for free of course)! Trying new frameworks is as-easy-as clicking a single button on Diploi, so you can focus on the fun parts, not the setup. Check us out at [https://diploi.com/](https://diploi.com) ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Skip the YAML and Server Configs: 7 Easy Deployment Platforms You Haven’t Tried > We created a list of deployment platforms (us included) that you should check out to make your development workflow faster Javier May 27, 2025 Updated October 28, 2025 ###### DevOps can be painful. We know from experience 🤕 ###### So we decided to create a list of new deployment platforms (us included) that aim to make the process of hosting your application online a smooth and maybe even enjoyable process --- By now you know both the big boys, like Azure, and you also probably know other platforms focused on making DevOps for non-DevOps people into a bearable experience, eg. Netlify, etc But I bet that you probably don’t know the ones I’ll present now, and I hope you find them useful, reliable, interesting, and maybe even in some cases, whimsical 😌 Let’s get started! ## Table of contents - [Canine](#canine) - [Sherpa](#sherpa) - [Sliplane](#sliplane) - [Ploi](#ploi) - [Stacktape](#stacktape) - [Thunder](#thunder) - [Diploi](#diploi) - [Choosing the Right Platform](#choosing-the-right-platform) - [References](#references) --- ## Canine > “A modern, open source alternative to Heroku” Canine is an open-source platform designed to simplify deploying apps to Kubernetes, similar to how Heroku simplifies app deployment. Created to fight the growing complexity and cost of IT infrastructure, especially with the addition of tools and vendors, many of which have open-source alternatives Canine addresses these challenges by providing a streamlined, Kubernetes-based solution that abstracts away much of the complexity, allowing small teams to manage their infrastructure more efficiently. It focuses on essential Kubernetes features and integrates with third-party applications via Helm charts. The goal is to minimize complexity, reduce costs, and manage infrastructure for developers ### Provides managed servers or clusters? No, you must host your server or cluster separately ### Anything free? 100% open source platform and currently free ### Pricing? For now, Canine is totally free ### Something else? Canine has add-ons that allow you to launch additional services, like Metabase or Elasticsearch on any cluster managed through Canine ### Video demo? --- ## Sherpa > “Deploy Sveltekit/Next.js/React/Docker Apps The Easy Way” Sherpa is a deployment platform designed to simplify the process of building, deploying, and scaling applications globally with significantly lower costs compared to competitors like Vercel and Netlify. It supports Next.js, Sveltekit, React, PayloadCMS, and Dockerized applications Another interesting fact about Sherpa is its pricing, which offers flat rates with no additional charges for seats or projects, and its competitive pricing is achieved by running its own servers and partnerships with Hetzner for global infrastructure, instead of relying on cloud providers like AWS ### Provides managed servers or clusters? Yes, Sherpa provides its own servers and uses Hetzner for global provisioning ### Anything free? Sherpa offers a free trial period and allows you to host 1 application ### Pricing? Starts with us$14.99 per month or us$119.88 per year for the Hobby plan. Sherpa offers 5 different pricing tiers for teams and enterprise ### Something else? Sherpa offers unlimited Edge requests, so you can scale freely without forced costly upgrades ### Video demo? \_ --- ## Sliplane > “Simple Docker Hosting Solution” Sliplane is a platform for deploying containerized applications, handling tasks like building images, running containers, health checks, and environment management. It offers continuous deployment by integrating with GitHub repositories and allows direct deployment from Docker Hub You are charged based on the servers you use, which are provided by Hetzner, with pricing starting at €9 per month plus VAT, which allows you to host unlimited containers on each server. The platform also provides tools for log monitoring, secrets management, and secure server configuration ### Provides managed servers or clusters? Yes, Sliplane uses Hetzner to provide servers to run Docker containers ### Anything free? Sliplane offers a trial period so you can test out their service ### Pricing? Servers start at €9 per month for their smallest server ### Something else? Sliplane has an API, which allows you to control their deployments and launch servers without a GUI ### Video demo? --- ## Ploi > “Deploy your next server in a few clicks.” Ploi is a server management platform designed to simplify DevOps for developers. You can add a server you want to manage, using any of their native integrations, like Hetzner and UpCloud, or using any custom server, eg. AWS or Azure, which can be done by adding Ploi’s public SSH key to your custom server After adding a server, Ploi first takes care of the configuration required for your server to host an application. Once the configuration process is complete, you can add “sites” which is where you manage the apps that will be hosted on a server Additionally, Ploi has a marketplace where you can add custom scripts, which expand what’s possible, eg. Installing Docker with a single click, allowing you to add additional services and utilities without directly accessing your server via SSH ### Provides managed servers or clusters? No, you can either add API access to one of the cloud providers supported by Ploi to launch servers quickly or you can launch a server on other cloud providers and use Ploi to manage it ### Anything free? Ploi has a free 5-day trial, which lets you try out most features of the product, excluding server monitoring and team management features ### Pricing? Ploi’s service starts at €8 per month for the basic plan ### Something else? Ploi also offers a version of their platform, designed for web hosting companies who want to provide a better user experience for their customers ### Video demo? --- ## Stacktape > “97% of AWS capabilities, 3% complexity” Stacktape is a deployment tool that automates the process of deploying applications on AWS by breaking it into several phases: resolving and validating configuration, building and packaging code, creating initial resources, uploading artifacts, and deploying infrastructure It uses AWS CloudFormation to manage infrastructure resources and offers features like caching, parallel uploads, and a hot swap mode to speed up deployments. In practice, you write a `stacktape.yml` file in your repo (choosing things like Lambdas, containers, and databases), and Stacktape builds the necessary CloudFormation under the hood Stacktape also ensures consistent naming conventions for resources and provides a console for inspecting deployed resources and CloudFormation templates. Additionally, it supports third-party services through CloudFormation extensions and uses direct AWS API calls for functionalities beyond CloudFormation’s scope ### Provides managed servers or clusters? No, you must have an AWS account, which you can then manage through Stacktape ### Anything free? Stacktape offers a free tier of their service which allows you to connect 1 AWS account and manage up to 10 deployments with most features enabled ### Pricing? Including the free tier, Stacktape offers a pay-as-you-go plan, which calculates the fees as a percentage of the AWS costs, and a fully managed plan starting at us$990 per month ### Something else? Stacktape has a CLI to enable you to deploy and manage their environments from the terminal ### Video demo? --- ## Thunder > “The deployment platform for modern web developers” Thunder is a platform that simplifies deploying modern web applications on AWS, supporting modern frameworks and workflows. To get started, you must sign up with GitHub and authorize the Thunder OAuth app, which sets up your account and organization. Organizations act as containers for applications, AWS accounts, and billing. You can connect multiple AWS accounts, and Thunder creates IAM roles to manage infrastructure provisioning After you set up your AWS account, you can import repositories from GitHub and start a deployment. Thunder installs a CDK stack on your AWS account when you import a new repository, enabling the deployment of single-page applications (SPA) and static site generators (SSG) using **CDK-SPA**, an open-source AWS CDK stack. The stack provisions an **S3 hosting bucket** and a **globally distributed CloudFront CDN** for your application Deployment is automated via **CodePipeline**, which triggers a build and publishes updates to S3 while invalidating the CDN cache. This setup ensures efficient hosting and distribution of static content ### Provides managed servers or clusters? No, you must have an AWS account, which you can then manage through Thunder ### Anything free? Thunder offers a free tier that allows you to launch and manage single-page apps and static sites, and provides CI/CD pipelines using CodePipeline ### Pricing? On top of the free tier, offer a Pro plan subscription for us$10 per month and a Lifetime license, only available while they are in beta, for us$99 which includes all features from the Pro plan ### Something else? Thunder handles HTTP response headers by providing default settings which you can also override and add custom headers using path patterns ### Video demo? Unfortunately, I couldn’t find a video demo, but you can try it for free by just registering with GitHub and adding your AWS account to start a deployment --- ## Diploi > “Magical Developer Experience” Diploi is a platform designed to simplify the process of building, managing, and hosting full applications without the need for DevOps. It uses a component-driven architecture, allowing you to select from a variety of frameworks and databases to define their application stack, which is stored inside of a `diploi.yaml` file allowing modification to the user’s selected stack Projects created with Diploi features Components, which serve as the basic building blocks for frontend, backend, or fullstack applications, and Add-ons, which can be combined with Components into a single deployment, simplifying how infrastructure is managed for web applications ### Provides managed servers or clusters? Yes, Diploi provides managed servers, which are used to run a cluster per deployment launched, from which Components and Add-ons are run as Docker containers ### Anything free? Diploi provides €50 free credits when you register to try out the platform ### Pricing? All prices on Diploi are based on the time that environments are online, which starts at 0,026€ per hour for their smallest cluster size ### Something else? Diploi provides remote development environments, which allow you to work on your applications without running locally. You can start coding on a remote development environment by using VS Code server provided by Diploi, or connect your preferred IDE (eg. VS Code, Cursor) to connect to your development environment ### Video demo? --- ## Choosing the Right Platform Each of these tools avoids heavy YAML or server config in their own way: - **Diploi:** Best if you want a turnkey full-stack environment (frontend + backend + DB) launched from boilerplate code, with minimal setup - **Canine:** Best for developers seeking a Heroku-like experience to run Kubernetes clusters, with one-click deployments, SSL certificates autogenerated, and autoscaling, while enabling cost-effective hosting on providers like Hetzner or DigitalOcean - **Sherpa:** Great for pure JS/Next.js/Docker apps where you just want to link Git and deploy globally on a budget - **Sliplane:** Ideal if your app is already containerized and you want simple Docker hosting with flat-rate pricing - **Ploi:** Suited for teams managing their own VPS/cloud servers who still want one-click provisioning and site deployment (WordPress, Laravel, etc.) without manual Nginx/SSL setup - **Stacktape:** Good for those who want AWS-grade services (databases, functions, auto-scaling) without wrestling with CloudFormation, it’s a PaaS on top of AWS using simple YAML - **Thunder:** Perfect for static sites and SSG apps (Astro, Next, Vue, etc.) that should be served from S3/CloudFront. It’s Git-driven and very cost-effective for front-end workloads Ultimately, the best choice depends on your stack and budget. All these platforms let solo devs and teams focus on code instead of config. They each automate the messy parts of deployment (YAML, servers, scaling) so you can deliver apps faster --- Do you know other platforms I should add to the list? Let me know! --- In case you are curious, [Test-drive Diploi ✨](https://diploi.com/) --- ## References ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Diploi Changelog: Browser IDE & Quick Trials > Hi everyone, we've been quiet here for a month, but not idle. First, a Big thank you 🙏 to everyone... Marcus April 3, 2024 [Read on Dev.to](https://dev.to/diploi/diploi-changelog-browser-ide-quick-trials-1n1c) Hi everyone, we've been quiet here for a month, but not idle. First, a Big thank you 🙏 to everyone who has participated in our pilots. It means the world to us and the feedback is invaluable. Now, on to the news 📰 ... ## 1) Browser IDE Previously, development using Diploi was done using the [Remote Development](https://code.visualstudio.com/docs/remote/ssh) feature of (mostly) VS Code, so users connected using ssh and edited in their local VS Code. This feature is great, and still available in all of our templates. But from this week on there is another option: Developing directly in the browser using a version of VS Code (a little like GitHub Codespaces). It's simple, you just click a button to open the editor. Almost all extensions work. This is great for quick edits, but I find you quickly forget it is in the browser so it is not only for minor work IMO. ## 2) Quick Trials People are so busy nowadays, we know that. That's why we created a way of trying out Diploi in only two clicks. No registration, no configuration, and with the Browser IDE you can start coding in the browser in no time. You get a full environment with database and everything to play with. If you like it you can claim the account with your GitHub account and continue working. [Check it out](https://diploi.com/launch) 🙌. It's a perfect way to try out our templates. Thank you for your time. We'll be back with more news soon. ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Diploi Receives Pre-Seed Funding > Diploi has completed its first pre-seed funding round. Founded in 2024 with the ultimate goal of taking away the pain of software development by letting developers focus on their main task - to develop new and better software. Patrik September 27, 2024 Updated October 28, 2025 Diploi, a SaaS service for managing, developing and hosting software applications, has completed its pre-seed funding round. Founded in 2024 by the team of _Marcus Ahlfors_, _Patrik Lindberg_, _Tuomas Pöyry_ and _Ville-Pekka Lahti_ with the ultimate goal of taking away the pain of software development by letting developers focus on their main task - developing new and better software. The team built a pilot of the cloud-based service in the spring of 2024, taking on trial users and its first customers. Discussions with business angels through the Finnish Business Angel Network, FIBAN, began, resulting in eight business angels together with the Angel CoFund investment fund participating in the completion of a pre-seed funding round of 255,000 euros. This will enable the team to further develop the Diploi service and platform to cover more technology tools, streamline product offering and develop a go-to-market strategy for the near future. Diploi aims to offer a uniform SaaS solution supporting the life span of the user’s application from development to production. The solution integrates main developer tools and processes into one coherent space, enabling developers and testers to fully focus on high quality development, minimizing setup and management needs. The Diploi team members have long-time experience in delivering software solutions and services to both B2B and B2C customers, covering everything from startups and SMBs to publicly traded companies. For more information, please contact\ CEO _Marcus Ahlfors_,\ +358 41 515 8726 ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # 🗺️ Diploi Roadmap for 2024 > We’ve been hard at work building Diploi, and now that we got funded 🎉, the pace is only going to... Tuomas October 3, 2024 [Read on Dev.to](https://dev.to/diploi/diploi-roadmap-for-2024-1nde) We’ve been hard at work building [Diploi](https://diploi.com/), and now that [we got funded](https://diploi.com/blog/diploi-received-pre-seed-funding) 🎉, the pace is only going to accelerate! Many of you have been asking for a roadmap, and we hear you!\ Below is a list of features, prioritized by importance, that will be coming in the near future. We will be publishing a dedicated article for each one, starting with the Stack Builder in the coming weeks. --- ## 1. 🧰 Stack Builder - A pick-and-choose-style tech stack builder - Easily combine different components to create any stack - Choose a pre-made stack with example code and add your own addons --- ## 2. 📝 Configuration-as-Code - Share a Diploi project simply by sharing its repository - Modify your entire infrastructure with code - Easily maintain different infrastructure setups on different branches --- ## 3. 🌍 Community Stacks - One-click sharing of pre-made stacks with example code - Access a constantly expanding library of community-made stacks for any occasion - Get rewarded when your shared stacks are used by others --- ## 4. 🔮 Future - Status monitoring, history and alerts - Improved logging - Cloud-agnostic deployments and self-hosting options --- That’s a wrap for what's currently in our pipeline! 🙏 We can't wait to get these features in your hands. If you’d like to be part of a closed group of testers, let us know! We’re always looking for developers eager to try out new features. ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Diploi Stack Builder > In our previous blog post we opened up our future plans in the form of a roadmap. We also promised to... Tuomas November 6, 2024 [Read on Dev.to](https://dev.to/diploi/diploi-stack-builder-32n4) In our [previous blog post](https://dev.to/diploi/diploi-roadmap-for-2024-1nde) we opened up our future plans in the form of a roadmap. We also promised to write more detailed posts on each item, and this post is the first. ## What is a Stack Builder? [Diploi](https://diploi.com/), our tool to run development & production environments, needs to know the infrastructure for each environment. Until now, someone needed to manually create a template with example code, HELM charts, and everything else Diploi required in order to work. This was quite hard if you had never worked on HELM or Kubernetes before. We want to make it easy for everyone to build a custom tech stack in seconds, without previous knowledge of Kubernetes or Diploi. Enter the Stack Builder. --- ## How it Works When you open the builder, you'll get a list of official and community made stacks that are ready to use and include working example code. If you pick one of these pre-made stacks, you can still modify them with extra add-ons like databases and services. If you need more control, you can switch to a custom stack, where you may pick all the components yourself.\ For example, you could pick a stack with Node.js front-end and a Laravel backend with a PostgreSQL DB and a Redis cache. All pre-configured and ready to go with a few clicks. After you have made your selection, Diploi will build a monorepo for your with all the required code to get you started. With one click, you have a ready-to-go remote code environment with the stack you just built. --- ## How it Works on a Deeper Level As you create your stack, we compose a `diploi.yaml` file for you. This will include all the components and add-ons for your stack, and some neat configuration to import & export env values and so on. This file can be updated in your code editor, and your infrastructure will automatically adapt to the changes. This means that environments in Diploi are fully configured as code. As we create the monorepo, we also include GitHub actions to build your components, HELM charts to run the internal Kubernetes cluster, setup the required packages for your development environment, and so on. --- ## When Can You Test It? We are currently working with a small internal testing group to iron out the experience. We aim to have a public beta up and running by the end of the year, so keep your eyes open! ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Easily Create Complex Stacks in Just a Few Clicks — New Release! > Previously, we wrote about our IaC implementation, and today we are proud to announce its public... Tuomas March 17, 2025 [Read on Dev.to](https://dev.to/diploi/easily-create-complex-stacks-in-just-a-few-clicks-new-release-3gdl) Previously, we wrote about our [IaC implementation](https://dev.to/diploi/how-we-solved-infrastructure-as-code-2ldn), and today we are proud to announce its public release. Our new Stack Builder is out for anyone to try out! 🎉 Head over to [diploi.com](https://diploi.com/) to have a go with it. Here's a concise list of what this new update makes possible: - 🖱️ Pick 'n' choose style UI for creating tech stacks - 🔌 Zero-config deployments for even the most challenging of stacks - 🪄 Automatic monorepo generation & configuration - 🔥 Automatic image generation for optimized production deployments - 🔧 Access to Dockerfiles for each component for full customizability These are in addition to what Diploi already offers, like our remote development environments with Cloud IDE & SSH support and automatic SSL generation to name a few. Below is a deeper dive to some key highlights of this update. I'll also reveal a few behind the scenes details on how we implemented these features 😉, so keep reading if you are interested! --- ## 🏗️ Visual Stack Builder Before this update, we supported a list of pre-made stacks with services that could not be easily swapped out for others. Like a template with Next.js and PostgreSQL could not be easily changed to include Redis for example. The most common feedback we received (by far) was the lack of support for the exact stack someone was familiar with and wanted to use. So we set out to fix this issue (and the solution had to be magical 🪄). What we ended up implementing is a one of a kind tool for easily building the exact stack that your project needs while still remaining flexible once the project grows or changes in scope. Our Stack Builder combined with the IaC `diploi.yaml` file allows you to change infrastructure on the fly, and because the file is committed to Git, even maintain different infrastructure on different branches 🤯!   Once you have picked your ideal stack, here's what our system does behind the scenes: - Creates a monorepo with boilerplate code for each component - Preconfigures GitHub actions to create optimized production builds - Generates HELM charts to set up environments with - Generates domains & SSL certificates for component endpoints 👀 We also implemented an embedded version of the full stack builder on our [diploi.com](https://diploi.com/) homepage. You can launch a stack directly from it without even creating an account. Give it a try if you are interested! --- ## 📝 Infrastructure as Code (IaC) I won't go into too much detail here, as you can check out the [IaC implementation](https://dev.to/diploi/how-we-solved-infrastructure-as-code-2ldn) blog post that goes into great detail about our IaC implementation. I do want to give an example of the `diploi.yaml` file here to give you an idea of what our Stack Builder actually generates as an output.   This file is committed to your repository, and can be changed at any time. It makes managing your infrastructure as easy as installing an NPM package. --- ## ⚙️ GitHub Actions While giving our users the freedom to edit their stacks the way they liked, we still wanted to give them the most optimized production environments possible, which means building optimized Docker images. We wanted to use GitHub actions for this task as GitHub actions make it convenient to run CI/CD tasks (like building production ready images) right in the project repository, and a lot of developers like using them in their workflow. We created two custom GitHub actions to make this as easy for the user as possible: - A "Define Components" action that reads the `diploi.yaml` file directly from the repository and builds a list of components that need to have images built - A "Build" action that configures and builds a single component We then create a matrix step from the output of the Define Components action, which allows us to run the Build action for each of the components. This way we do not need to edit the GitHub actions file at all even when the components change!   We allow customizing the Dockerfiles for each of these components directly inside of the project repository, so you can tweak these builds to your liking. Both of these actions are actually open source, so check them out at our GitHub:\ 👉 [diploi/action-components](https://github.com/diploi/action-components)\ 👉 [diploi/action-build](https://github.com/diploi/action-build) --- That's all we have for now! If you have any questions, feel free to leave a comment on this post 🙏. And check out our new Stack Builder directly on [diploi.com](https://diploi.com/)! ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Exploring 7 Lesser Known AI Coding Extensions for VS Code > In this article, we check interesting AI coding alternatives to the popular AI coding tools in the Visual Studio Marketplace Javier September 18, 2025 Updated October 28, 2025 ###### Beyond the popular tools that most people are using If you code for a living or just got started in the journey to become a developer, I imagine you are aware of how helpful AI can be, but chances are that you are aware of the usual suspects, like GitHub Copilot or OpenAI Codex. --- I have heard so much about the same 4 or 5 tools already that I got fed up and wondered, what else is out there? So I decided to explore some lesser known tools that might be interesting too, and who knows, maybe even better. In this post, I explore seven AI coding extensions for VS Code that you probably haven’t heard about, covering: - Supported AI models - Features - Pricing - Voice Support - Context Window - MCP / Tools - Privacy & Security And at the end, I provide a short conclusion based on the findings. [TLDR? Check the comparison tables](#comparing-the-extensions) --- ## Table of contents - [List of AI coding extensions explored in this article](#list-of-ai-coding-extensions-explored-in-this-article) - [Comparing the Extensions](#comparing-the-extensions) - [Closing thoughts](#closing-thoughts) - [References](#references) ## List of AI coding extensions explored in this article We’ll go over the following extensions: - [**Sixth AI**](#sixth-ai---the-all-in-one-coding-agent) - [**Code Web Chat**](#code-web-chat-cwc---chatgpt-in-your-vs-code) - [**Syntx Agentic workflow**](#syntx---autonomous-ai-agent-in-your-editor) - [**Tabby**](#tabby---self-hosted-copilot-alternative) - [**Augment code**](#augment-code---the-professionals-ai-copilot-with-superpowers) - [**GoCodeo**](#gocodeo---build--ship-apps-with-an-ai-agent) - [**Vibe Coder**](#vibe-coder---voice-driven-coding-with-ai) **Let’s get started!** --- ### Sixth AI - The All-in-One Coding Agent Official website: VS Code Marketplace listing: GitHub: Sixth offers code autocompletion, chat mode, debugging, agentic mode, and codebase search. You can ask it to refactor a function, and it will apply changes across files through the chat interface. It also integrates with VS Code’s inline editing (you can highlight code and get suggestions in-place) and CodeLens for explanations and one-click refactors, plus it can be integrated with Model Context Protocol (MCP) servers to extend the AI’s capabilities. #### Supported AI models Sixth works with the most popular AI models and allows you to use custom models through HuggingFace. The full list of models supported by Sixth include: - Groq - Cohere Command - HuggingFace - Nomic - Voyage AI - Cerebras Instruct - SambaNova - Pixtral Large - Llama 4 Maverick - Llama 3.1 - Llama 3 - Qwen 3 - Qwen 2.5 Coder - Qwen Plus Latest - Qwen Plus - Qwen Turbo Latest - Qwen Turbo - Qwen Max - Doubao 1.5 Pro - Doubao - Grok 4 - Grok 3 Beta - Grok 3 Fast Beta - Grok 3 Mini Betax - Grok 3 - Grok Beta - Grok Vision Beta - DeepSeek R1 - DeepSeek Chat - DeepSeek Coder - Amazon Nova Premier - Amazon Nova Pro - Amazon Nova Lite - Amazon Nova Micro - Mistral Large - Mistral Small - Ministral - Codestral - Devstral Small - GPT-5 - GPT-5-mini - GPT-4.1 - GPT-4o - GPT-4o Mini - GPT-4 Turbo - GPT-4 - GPT-3.5 Turbo - o4 Mini - o3 - o1 Preview - o1 Mini - Gemini 2.5 Pro - Gemini 2.5 Flash - Gemini 2.5 Flash Lite - Gemini Pro - Gemini 1.5 Pro - Gemini 1.5 Flash - Claude Sonnet 4 - Claude Opus 4.1 - Claude Opus 4 - Claude 3.7 Sonnet - Claude 3.5 Sonnet - Claude 3.5 Haiku - Claude 3 Opus - Claude 3 Haiku #### Features When you use **Sixth**, you get a two-phase workflow and editor-native helpers: - **Plan and Act modes** - **Plan** > Sixth reads your codebase, asks clarifying questions, and helps design an approach without touching files. It’s meant for scoping, exploring structure, and de-risking changes. - **Act** > Once you’re happy with the plan, Sixth can implement it, making edits across files while keeping the planning context. You approve changes as it go. - **Editor integrations** - **Inline/CodeLens actions and code commands** for explanations, fixes, and refactors directly in the file. - **Terminal helper (“See Terminal”)** to generate shell commands from natural language. - **Project-aware chat and codebase indexing** so the agent can navigate and modify multiple files in one flow. Under the hood, Sixth can **read/write files, run commands, use a browser tool, and extend itself via MCP servers**, which all require explicit approvals unless you enable auto-approve. #### Pricing Sixth has a free tier with limits, and if you want to take advantage of MCP servers and agentic functionality regularly, Sixth offers paid plans, starting at $10/month. Neither the free or paid tiers of Sixth require you to have your own API keys for the models you want to use. #### Voice Support At the moment, Sixth doesn’t support voice input and all interaction is via chat, inline edits, and commands in VS Code. #### Context Window Sixth actively builds context in two ways: automatic file exploration and user-guided context. Additionally, it shows a context progress bar so you can see how many tokens could still be processed before reaching the context window’s limit. #### MCP / Tools Sixth allows you to use MCP servers from their marketplace or by adding your own custom remote server, to extend the capabilities of Sixth. #### Privacy & Security Relevant links: Sixth hasn’t have published a privacy policy or terms of service on their homepage, which is a major oversight given that it would be the bare minimum for these kinds of products. The closest documents I could find related to how data is handled was about how the use telemetry data and a security concerns page. Based on those documents, Sixth discloses that the VS Code extension has no server-side components and it connects directly to your chosen AI endpoints. They also have a zero-data-retention policy for code, so code and responses aren’t collected. Another point that stands out is their claim about Sixth being open-source, which it is not available on their official GitHub profile and seems odd since there’s no evidence in the document to verify that claim. If you know of a different repository where they are hosting their code, please let me know. #### Conclusion Sixth provides multiple features within one extension, like code completion, agentic actions like browser navigation, multiple-file changes and MCP actions. You can ask questions about your codebase, generate documentation, and also execute shell commands using the terminal. I believe that Sixth is a young startup, and I understand they still need to polish the product, but the lack of clear privacy policies, terms of service and transparency disclaimers makes me a bit worried about the legitimacy of this extension. I hope I’m being paranoid and it’s all good, but we’ll see. That said, I think Sixth has a lot of potential and I believe that it’s worth giving it a try if you are looking for a solution that could give you access to multiple AI models, without the need to manage API keys or individual payments to each AI provider you want to use. --- ### Code Web Chat (CWC) - ChatGPT in Your VS Code Official site: VS Code Marketplace listing: GitHub: Code Web Chat is a free, open-source VS Code extension that connects your editor to AI chatbots in your web browser, which acts as a bridge between VS Code and all those web AI chat interfaces (ChatGPT, Claude, Bard/Gemini, etc.). Instead of copying code to ChatGPT and back, CWC lets you do it in one flow: - You select files or code in VS Code - Type an instruction (like “Optimize this function” or “Explain this code”), - And it will automatically open your browser and initialize a chat with the AI of your choice, pre-loaded with the selected code and prompt - When the AI responds in the browser, CWC adds an “Apply” button so you can insert the answer back into your code with one click _Source:_ To use CWC, you need to install the VS Code extension and then install the browser extension, because as I mentioned above, your prompt and context will be sent to the chatbot you choose to use. For example, you can use regular ChatGPT (free or Plus version) or other free chatbots via their web interfaces, without API keys or payments to the AI provider needed. Essentially, if there’s a web-based AI that can help with coding, CWC likely supports it. ed AI models #### Supported AI models CWC supports some of the most popular chatbots and interacts with them via their web interface. This is the full list: - AI Studio - ChatGPT - Claude - DeepSeek - Doubao - Gemini - Grok - Kimi - Mistral - Open WebUI - OpenRouter Chat - Perplexity - Qwen - Together - Yuanbao - Z.AI #### Features By installing the companion browser extension ([Chrome](https://chromewebstore.google.com/detail/code-web-chat-connector/ljookipcanaglfaocjbgdicfbdhhjffp) and [Firefox](https://addons.mozilla.org/en-US/firefox/addon/code-web-chat-connector/)), CWC can launch these chats and inject your prompt and context hands-free. The extension doesn’t store the AI’s input or output, and you can review the answers before explicitly clicking “Apply” to paste the AI’s response inside your code editor. Besides the browser chats, CWC also includes some basic API-based tools: you can configure an OpenAI-compatible API key (OpenAI, Azure, or local OAI-like APIs) to get inline code completions or run edits within VS Code. So it offers both real-time completions (like Copilot style) and the multi-file chat workflow. #### Pricing Code Web Chat is MIT-licensed open source software and doesn’t charge anything. It’s a community-driven “free forever” project. The only costs would be optional: e.g. if you use an API that charges money (OpenAI API usage) or if you decide to donate to the developer. Otherwise, by using the free web UIs of AI models, you avoid paying. #### Voice Support There’s no voice control in CWC, it’s all text-based. However, since it works with browser chat UIs, you could technically use something like Chrome’s voice typing or a browser extension for voice if you really wanted to dictate, but natively, CWC doesn’t handle voice commands. #### Context Window CWC’s workflow allows a multi-file context. You can select multiple files or sections in VS Code and send them together to an AI chat prompt. The limitation is whatever the target AI’s context size is (ChatGPT has its token limit, Claude has its larger context, etc.). There’s no fancy vector database or code indexing here, it’s a funnel to the AI’s UI chat interface. #### MCP / Tools This extension doesn’t integrate with MCPs or tool use, because its philosophy is to keep things local and simple. It doesn’t run external commands and it just hands off to web AIs and brings back the results. #### Privacy & Security Relevant links: CWC claims that it doesn’t collect telemetry or stash your code. The code you select is sent to the AI in your web browser, just as if you pasted it yourself. Since it’s open source, you can inspect their claims. #### Conclusion In a nutshell, Code Web Chat turns your browser into a sidekick for VS Code. It’s lightweight and focused, with no complex features to configure. You do need to install a browser plugin and keep a browser open. I think this tool is best suited for devs who want to save money and don’t need complex features. It’s not as streamlined as other extensions explored here, but it gets the job done for simple tasks. --- ### Syntx - Autonomous AI Agent in Your Editor Official site: VS Code Marketplace listing: GitHub: Syntx is an AI autonomous coding agent that works in VS Code, which started as a fork of the popular Roo-Code AI coding extension. It can read and write files in your project, run terminal commands, automate browser tasks, and integrate with popular AI models and custom models. models #### Supported AI models Syntx allows multiple AI API providers, so you can access different proprietary models, either by adding your own API keys or through Syntx. Additionally, it allows you also use your own AI models, using LM Studio or Ollama. The complete list of API providers includes: - Amazon Bedrock - Anthropic - Chutes AI - Claude Code - DeepSeek - GCP Vertex AI - Glama - Google Gemini - Groq - Human Relay - LiteLLM - LM Studio - Mistral - Ollama - OpenAI - OpenAI Compatible - OpenRouter - Requesty - SyntX - Unbound - VS Code LM API - xAI (Grok) If you use Syntx as your default provider, you can use the following models: - claude-opus-4-20250514 - claude-sonnet-4-20250514 - claude-3-7-sonnet-latest - claude-3-5-sonnet-latest - claude-3-5-haiku-latest - claude-opus-4-20250514-thinking - claude-sonnet-4-20250514-thinking - claude-3-7-sonnet-latest-thinking - gpt-5 - gpt-4.1 - gpt-4.1-mini - gpt-4.1-nano - o3-mini - o4-mini - llama-3.3-70b-versatile - meta-llama/llama-4-scout-17b-16e-instruct - qwen-qwq-32b - deepseek-r1-distill-llama-70b - Kimi-K2 - perplexity-sonar-pro - perplexity-sonar - perplexity-sonar-premium - perplexity-r1-1776 - perplexity-sonar-reasoning-pro - perplexity-sonar-reasoning - gemini-2.5-flash - gemini-2.5-pro - gemini-2.5-flash-thinking - gemini-2.5-pro-thinking - deepseek-v3 - deepseek-v3-premium - Grok-4 - openrouter-deepseek-r1 - openrouter-claude-sonnet-4 - openrouter-gemini-2.5-pro - openrouter-codestral-2501 - openrouter-magistral-medium-thinking - openrouter-devstral-small - GLM-4.5 - qwen3-coder - gpt-oss #### Features When you use Syntx, you’re not limited to one mode of operation. It provides multiple “Modes” or personas you can switch between depending on what you need. The available modes are: - Plan > Intended to first prepare the assistant, based on your app’s context, and it prepares the actions that the agent must follow - Code > Allows for code editing and generation inside your files - Chat > Which lets you make questions about your code - Debug > Used for code reviewing and fixing issues - Orchestrator > Which can be used to combine the other modes to execute complex operations Additionally, it allows you to create custom modes, so you could, for example, create a mode to generate documentation or security audits. The use of modes gives Syntx the possibility to adapt its style and the tools it uses based on context. #### Pricing Syntx’s extension is free to use if you use an API provider, and you only pay for the credits you consume through those providers or infrastructure costs if you host your own modes. Syntx, as an API provider, allows some free usage, but there’s no free tier and doesn’t have a trial to explore all features in-depth, which might be limiting if you want to test Syntx as your API provider without paying for an extended period of time. If you choose to use Syntx as your default provider, they charge $1 per credit plus a 15% platform fee + 3.37% processing fee, which amounts to $1.19 per credit. #### Voice Support At the moment, Syntx doesn’t have voice capabilities and it only operates through the chat interface and command palette. You type commands/instructions and the AI executes them. #### Context Window Syntx can read multiple files, it can open and inspect parts of your project as needed, but it doesn’t index all files in your project proactively. #### MCP / Tools Syntx also has agentic capabilities via MCP servers and it can perform actions inside of your code on demand. Some actions include: - Create, modify, or delete any file in your workspace files. - Run shell commands in the VS Code terminal, so it can run your build, or git commands, etc., on request. - Control a browser and automate actions to fetch info or run a web-based tool. - Use external MCP tools, allowing you to plug in community or custom tools. MCP support means you could, for example, add a tool that calls an API or queries documentation, and Syntx’s AI could invoke that as part of solving a task. Syntx will execute commands only with your permission at each step. #### Privacy & Security Relevant links: Because Syntx allows you to bring your own model and it’s open-source, you can use AI in your codebase, sending all data only to the AI provider you prefer. Although if you use Syntx as your API provider, it means that your code will be exposed to Syntx as well. One important security aspect is that because Syntx can run commands and edit files, you should only use it in directories and with projects where you’re okay with those kind of operations. By default, Syntx will always ask for confirmation before performing an action. #### Conclusion Syntx offers code assistant capabilities, with a wide range of options and behaviours that allow for a lot of flexibility, for example, it figures out a plan and executes step by step, while confirming with you to make sure that it is only executing changes that you agree with. If you want to evaluate different models in your code or use different models for various tasks within your code, then Syntx will be an interesting option for you. --- ### Tabby - Self-Hosted Copilot Alternative Official site: VS Code Marketplace listing: GitHub: Tabby is an open-source, self-hosted AI coding assistant that provides code completions and a chat helper, much like GitHub Copilot, but you run it on your own machine or server. With Tabby, you must install the Tabby extension and also run the Tabby AI local server. The server hosts the actual AI models that generate code suggestions. The VS Code extension then communicates with this server to get completions or to answer questions. This architecture means your code and prompts stay within your environment. #### Supported AI models Tabby doesn’t come with a single huge pretrained model like GPT-4 (that wouldn’t be open source or lightweight). Instead, Tabby supports various open-source LLMs for code. You can choose from models like StarCoder, CodeLlama, Qwen, among other options that the Tabby team has integrated. They provide a Model Registry listing open source models that they support and they can be used for three different purposes: ##### Completion models - StarCoder-1B - StarCoder-3B - StarCoder-7B - StarCoder2-3B - StarCoder2-7B - CodeLlama-7B - CodeLlama-13B - DeepSeekCoder-1.3B - DeepSeekCoder-6.7B - CodeGemma-2B - CodeGemma-7B - CodeQwen-7B - Qwen2.5-Coder-0.5B - Qwen2.5-Coder-1.5B - Qwen2.5-Coder-3B - Qwen2.5-Coder-7B - Qwen2.5-Coder-14B - Codestral-22B - DeepSeek-Coder-V2-Lite ##### Chat models - Mistral-7B - CodeGemma-7B-Instruct - CodeQwen-7B-Chat - Qwen2.5-Coder-0.5B-Instruct - Qwen2.5-Coder-1.5B-Instruct - Qwen2.5-Coder-7B-Instruct - Qwen2.5-Coder-14B-Instruct - Qwen2.5-Coder-32B-Instruct - Qwen2-1.5B-Instruct - Qwen3-0.6B - Qwen3-1.7B - Qwen3-4B - Qwen3-8B - Qwen3-14B - Qwen3-32B - Qwen3-30B-A3B - Qwen3-235B-A22B - Codestral-22B - Yi-Coder-9B-Chat ##### Embedding models - Nomic-Embed-Text - Jina-Embeddings-V2-Code You can also specify your own model by following the [Tabby Model Specification](https://github.com/TabbyML/tabby/blob/main/MODEL_SPEC.md). #### Features Tabby’s primary feature is autocomplete, so as you type, it suggests the code you need, including multi-line suggestions and whole function bodies in real-time. It also has a chat Q\&A component, where you can ask questions about your code (e.g. “What does this function do?” or “How can I optimize this query?”) and it will answer, citing context from your code. There’s also an inline chat feature to give commands to modify selected code or generate via prompt (similar to Copilot’s “edit” functionality). Tabby also has a code browser, which allows you to explore files from your indexed repositories. #### Pricing Tabby is free, but if you’re working with a team with more than 5 users, then you need to buy a subscription. The base subscription costs $19/month per user, so for a team of 6, it would be $114/month. Tabby doesn’t charge you for inference, since you must handle the hosting for your AI models, so all compute costs would come from the hardware you use, rather than from Tabby. #### Voice Support Tabby doesn’t have support for voice commands. #### Context Window Tabby can index git repositories from GitHub, GitLab and docs, but it doesn’t index your local code. For chats, you can feed specific files within your code and docs, to tailor responses based on context. #### MCP / Tools It doesn’t support MCP servers or agentic behaviours. #### Privacy & Security Relevant links: With Tabby, you must use self-hosted models, so your code doesn’t leave your local environment. One point to note is that Tabby collects telemetry data on all self-hosted instances, which they claim is only used internally at Tabby. #### Conclusion In short, Tabby is the “roll your own” solution. It’s meant for those who value privacy and control over convenience. You might not get OpenAI-level IQ, but it won’t surprise you with large bills. For small projects or learning purposes, using Tabby can also teach you how AI code assistants work under the hood. It’s not the most plug-and-play tool out there, but if you are looking for a fully self-hosted solution, then Tabby is for you. --- ### Augment Code - The Professional’s AI Copilot with Superpowers Official site: VS Code Marketplace listing: GitHub: Augment is an AI coding extension can handle context indexing. Based on feedback from their community, it seems they have a better context engine than other popular tools like Cursor and Windsurf, although I couldn’t validate how true that is. #### Supported AI models The models available within Augment depend on the mode you need to use. If you use the Chat mode, then Augment uses its own model and it doesn’t have support for external models. When instead, you are using the agent mode (local or remote), then you can choose between **Claude Sonnet 4** or **OpenAI GPT-5**. #### Features Augment has multiple interesting features, with one of its core features being its Context Engine, which indexes your codebase to generate suggestions and chat responses that are context-aware across your project. Other features include: - **Agent mode:** An AI agent that can complete high-level tasks like “Add a new API endpoint for X” by planning and making multiple edits across files. It’s aware of your frameworks, dependencies, schemas, etc. - **Remote agent mode:** This mode uses the same agent as the local mode, but instead of running the agent locally, it runs it remotely, so you can use it in any environment. - **MCP servers:** Augment supports 100+ MCP tools and native integrations to expand what the agent can do. It ranges from database lookups to calling an external API during its reasoning. - **Chat with Smart Apply:** The chat interface allows for Q\&A with your codebase, but additionally, when it gives you an answer or code change, you can apply the suggested changes from the chat interface. - **Next Edit:** This feature is a guided workflow for multi-step code changes, for example, if renaming a function might require updating references, docs, tests, the workflow walks you through each update required. - **Inline Instructions and Completions:** You can use natural language to modify code directly inside your files, similar to how GitHub Copilot works. It can also do autocompletions as you type, which are based on the overall context of your project, rather than standalone suggestions. #### Pricing Augment Code is a closed-source, fully paid service, with a 7-day trial, which gives you code completions and Next Edit, and if you add a payment method, you get 50 chat messages free. They have 4 different pricing tiers and a custom plan for larger companies. Their prices start at $20/month. To get serious usage, you’d move to the Developer plan at $50/month, which gives you 600 messages/month and additional features like team collaboration and SOC2-grade security. They also have Pro $100/month for 1500 chat messages and Max $250/month for 4500 chat messages for higher volume. Completions and Next Edits are unlimited for all plans, while the message limits apply to chat/agent interactions. Regardless of your plan, if you exceed your message limit, Augment offers extra message packs of 100 messages for $15. #### Voice Support Augment doesn’t have voice control. It’s all text-based through their chat interface and code completions. #### Context Window Augment indexes your project folder, so the Context Engine can retrieve the most relevant pieces into the model, to keep code completions and chat constrained and cost-effective. If you have a multi-folder project, you can extend a project’s context by linking to other folders containing relevant code for your project. Beyond local files, Augment’s context can be extended with its tools and MCP servers. One example is the integration with GitHub, which can feed recent Git commit history so the Augment agent can reuse it to understand patterns and answer questions linked to previous changes, extending context beyond the current state of the code in your project. #### MCP / Tools Augment supports MCP servers so the Agent mode can use external tools and data sources, with one-click integrations for popular dev services like CircleCI, MongoDB, Redis, Honeycomb, Heroku, Render, and Vercel. You can also configure additional servers manually or import JSON configs. For control, Augment exposes tool permissions so you decide what the agent can do (e.g., running commands, editing files, calling integrations). #### Privacy & Security Relevant links: Augment claims that it doesn’t train its AI with your data, and all users get SOC 2 Type II compliance by default. Now, something confusing is that depending on what service tier you are using, their terms of service are different. For users on the Community tier, who are people using Augment code for free, the user’s code and the responses generated are used for training, while the Professional and Enterprise tiers are not used for code. I suspect that the Community tier is no longer available, but some users might still have access to it, which is why they still list the Community terms. #### Conclusion Augment positions itself as an agentic coding platform for large codebases, where you pay per user message, while “Next Edits” and completions are unlimited. Their Context Engine pulls the code, docs, and commit history into its responses, which adds an extra layer of accuracy. Additionally, their MCP support and integrations with other dev tools make it easy to wire build systems, databases, and deployment platforms to extend Augment’s capabilities beyond just coding. If you work with large codebases and need code completions and agentic capabilities with context awareness, then Augment is an interesting alternative for you to explore. --- ### GoCodeo - Build & Ship Apps with an AI Agent Official site: VS Code Marketplace listing: GitHub: **GoCodeo** is an AI coding agent that lives inside VS Code and helps you **ask**, **build**, and **test**, from scaffolding full-stack apps to one-click deploys. It ships with workflow models for **ASK**, **BUILD** and **TEST**. It also supports **MCP** to wire up tools like GitHub, Notion, Postgres, and Stripe, for example, so agents can fetch external context and perform multi-step actions. #### Supported AI models GoCodeo lets you pick models via a **Model Selector**, listing 4 providers and specific options that include: - Anthropic - Claude 3.5 Sonnet - Claude 4 Sonnet - OpenAI - GPT-4.1 - o4-Mini - GPT-4o Mini - Google - Gemini-2.5-Pro - DeepSeek - DeepSeek-R1 - DeepSeek-V3 In GoCodeo, you need to bring your own API key for each provider you wish to use. #### Features GoCodeo’s features cover a wide range of tasks, from general Q\&A to full-stack app development. Here’s the full list of features: - Different modes for specific tasks within your code, which include: - **ASK** This allows you to chat with the agent to **ask over documents and images**, use a **Terminal Helper** for command suggestions and a **Terminal Debugger** for failed commands, and keep an organized **chat history**. There’s also an **Enhance Prompt** helper that expands simple asks into richer specs. To access the ASK mode, you can use the shortcut: **Ctrl/Cmd + Shift + L** - **BUILD** Which is all about **scaffolding front-end and back-end codebases**, with the following frameworks: - **Front-end Templates** - React - Angular - Vue.js - Typescript - Vite - Next.js - Astro - Nuxt - Svelte - Remix - Slidev - Remotion - Qwik - Nativescript - **Back-end Templates** - Express.js - node.js - SpringBoot - Django - FastAPI - ASP.net - Ruby on Rails - Laravel - NestJS - Flask - Fastify - Gin - Echo - koa You can also use a visual **scaffolding** panel, **dependency management**, **build history**, and **one-click deploy** to Vercel. It also supports **Supabase** for auth/data. You can attach an **image to generate code**, and use **@ references** to target files/symbols. The BUILD mode shortcut is: **Ctrl/Cmd + Shift + K** - **TEST** Used to generate unit tests in multiple languages, and execute them with a built-in runner (e.g., Python/JS/Java/Go). You get **AI debugging insights**, and can apply **auto-fixes** when reviewing the results. - GoCodeo supports MCP servers, which can be declared in a `mcp.json` file, and allows you to add **Global MCP servers**, browse **community MCP servers**, and let the agent **auto-select** tools per request. You get **inline logs and reasoning** for each tool call. - **Context handling** by using **@Files** and **@Code** to reference file paths or specific code sections, plus the option to attach **documents/images** as context to generate answers. - **WebSearch (@Web)** powered by Perplexity, to find relevant documentation. - **Auto-generate README files** by analyzing repository contents - **GitHub pull-request assistance** to create and manage pull request, with reference generation. #### Pricing There are **two stories** depending on where you look: - On the **VS Code Marketplace**, GoCodeo’s FAQ says it’s **“now completely free because you bring your own API keys”**, with no per-token charges, and you control provider costs. - On GoCodeo’s **website pricing page**, there are tiers: - **Hobby (Free)** with quotas for premium model requests, autocompletions, and deployments - **Starter ($9/month)** and **Pro ($19/month)**, with higher limits, including daily Claude Sonnet allowances. In practice, this suggests two pricing models, one free where you **bring your own API keys**, and the other, which is paid, where you access the models via **GoCodeo-metered usage**, if you want built-in usage without managing keys. Although to me it seems odd that there are limits on the free tier, if you have to bring your own API key, I suppose it could be due to the costs generated from handling the requests that the extension has to perform. #### Voice Support GoCodeo doesn’t have built-in microphone/voice control in the VS Code extension. Interaction is all text-based for all ASK/BUILD/TEST modes. #### Context Window GoCodeo treats “context” as what you attach or reference, then streams only the relevant pieces to the model you pick: - @Files to reference files. - @Code to reference exact code snippets. - Document and image attachments (PDF/DOC, UI mocks) as additional context. #### MCP / Tools MCP servers must be manually set up in GoCodeo, which can be defined in an `mcp.json` file, and allows you to add **Global MCP servers**. The user experience is not as smooth as other AI extensions we explored so far. There are no additional integrations to other services inside GoCodeo. #### Privacy & Security Relevant links: GoCodeo doesn’t have standalone pages for terms of service or privacy policy on its homepage and instead has a “Terms of Use” page, which covers some points, but in a very short and generic way. They claim that your usage data might be used to improve their services, and that customer data is never shared or sold, but they don’t specify what they classify as usage data or customer data, or if your code is used for training. #### Conclusion GoCodeo seems ok to explore if you are comfortable with the lack of transparency around their data policies. Maybe they are just a young startup and they will improve their policies as they grow. Their lack of consistency around pricing is also odd, and it’s not clear if the limits apply as a trial or if they apply even if you add your own API keys. If you are an individual developer who likes to test out different tools, then GoCodeo might be a good option for you to explore. However, if you work at a company that has strict rules around data privacy, then I would avoid using this extension. --- ### Vibe Coder - Voice-Driven Coding with AI Official site: VS Code Marketplace listing: GitHub: Vibe Coder is a different flavor of AI coding assistant. Vibe Coder is a voice-first coding assistant by Deepgram, a company focused on voice assist. This extension lets you interact with VS Code and generate code using natural voice commands. **Important** Vibe Coder seems to be in a very early stage and hasn’t been updated in a while, which might explain why, while I was trying it, I couldn’t get the Vibe mode to work, so I can’t speak about its capabilities for vibe coding. The Code mode worked fine, and I’ll try it out in my workflow when writing blogs. #### Supported AI models Vibe Coder uses their own model for voice-to-text, and then they use OpenAI for the AI response generation, although from their documentation, it’s not clear what model they use, but from their repository, you can see that they use `gpt-4-turbo-preview`, and during testing it showed on my usage dashboard as **gpt-4-0125-preview**, which is the right model ID. I couldn’t find a way to change the model from the extension settings, but in theory, it should be possible by using the source code to self-host the extension. #### Features Since I couldn’t test the Vibe mode, I can only speak about the Code mode with certainty, but I’ll list other features that I found in the documentation and marketplace listing for Vibe Coder, and will separate them into two main categories, verified and unverified: ##### Verified features - Code mode (dictation and voice-to-text chat): Speak code/instructions, the extension sends your transcript to the DeepGram API for transcription, and then using customizable prompts (e.g., “debug this,” “fix typos,” “make it idiomatic ”), uses OpenAI to generate the response, and copies the result to your clipboard. - Cross-platform mic support: Uses SoX (macOS/Windows) or ALSA tools (Linux) for audio capture; includes commands to test and list microphones and per-OS device settings. ##### Unverified features - Vibe mode (voice agent): Brainstorm ideas, validate approaches, and even ask it to generate a product spec at the end of the conversation or code snippets. As I mentioned before, I couldn’t get this mode to work, so I can’t speak about its capabilities. - Voice commands and navigation: Sample commands include “open the file index.js,” “create a new file,” “show explorer,” “tell me about this codebase.” Besides these features, DeepGram claims in the Vibe Coder marketplace listing to be working on other future improvements like adding project context and MCP capabilities, but the last update of their extension was in February 2025, so I’m not sure if they are still actively working on it. #### Pricing Vibe Coder is free to use, but you need to provide your own API keys for DeepGram and OpenAI. There are no additional costs associated with using the extension. #### Voice Support Vibe-Coder is voice-first, all you need to do is open the Vibe Coder panel with `Cmd/Ctrl + Shift + V`, select the model you want to use, and start/stop dictation with `Cmd/Ctrl + Shift + D`. You can’t continuously talk to the agent, you need to stop and start the dictation to send the prompt to OpenAI to get a response. The extension includes cross-platform mic support and requires system audio tools (SoX on macOS/Windows, ALSA utilities on Linux) for capture. #### Context Window Vibe-Coder doesn’t have a way to index projects, which is odd since the Vibe mode would require a way to understand the context of the project to be useful. #### MCP / Tools There’s no MCP support yet. The public roadmap calls out “Add MCP capability to the Vibe mode agent,” indicating tool-calling via MCP is a future enhancement rather than a current feature. #### Privacy & Security Relevant links: The extension is open-source, so you can check their code, while the audio is sent to Deepgram for processing. The extension doesn’t store audio itself and all conversations are handled under Deepgram’s privacy policy. From the repository of Vibe Coder, it seems that once the audio is processed, it is then sent to OpenAI. DeepGram doesn’t have a privacy policy or terms of service for Vibe Coder, so it’s hard to know what they do with the audio and the conversations in the released extension. #### Conclusion Vibe Coder is an interesting initiative to explore voice-first coding, but as I mentioned, the fact that the product hasn’t been updated in the past months makes me question if it’s still actively maintained. If you want to experiment with voice coding, give Vibe Coder a try, although I couldn’t get the Vibe mode to work on my machine. 🥲 --- ## Comparing the Extensions In summary, let’s compare all extensions: ### Pricing Extension | Plans Sixth AI | Free with limits and paid from $10/month or $7/month if you take the annual plans. Code Web Chat | Free and also open source Syntx | Free if you bring your own API keys or paid if you use Syntx credits to access AI models, for $1 per credit + 15% platform fee + 3.37% Razorpay fee Tabby | Self-hosted models only, Free for up to 5 users, paid for teams $19/user/month up to 50 users and custom pricing for Enterprise Augment Code | No free plans, Entry tier $20/month, Developer $50/month, Pro $100/month, Max $250/month and Enterprise custom pricing GoCodeo | Free with limits or fully free if you bring your own API keys, paid plans Starter $9/month or $85/year, and Pro $19/month or $182/year Vibe Coder | Free to use, but you must bring your own API keys for Deepgram and OpenAI ### Code base indexing and context window Extension | Summary Sixth AI | Project indexing with automatic file exploration and user-guided context Code Web Chat | No indexing, sends selected code to the target web chatbot and it’s limited by that model’s context Syntx | No indexing, but you can add files to your chat prompts Tabby | No indexing, but you can add files to chat prompts Augment Code | Context Engine indexes the project folder and you can link additional folders GoCodeo | No indexing, but context can be added to prompts via @Files, @Code and attachments Vibe Coder | No indexing, but in Vibe mode, the assistant should, in theory, be able to read files ### MCP, tools and integrations Extension | Summary Sixth AI | MCP servers supported, can read/write files, run commands, use browser tool and terminal helper Code Web Chat | No MCP, browser connector to many chatbots Syntx | MCP servers supported, file edits, shell and browser automation with step approvals Tabby | No MCP, no browser tools or integrations Augment Code | MCP servers supported with easy integrations like CircleCI, MongoDB, and others GoCodeo | MCP support via mcp.json Vibe Coder | No MCP or other integrations ### Privacy and security Extension | Summary Sixth AI | Doesn’t sell data, and doesn’t use your code for training, closed source, routes requests via vendor servers, no published privacy policy or terms of service Code Web Chat | Doesn’t sell data, and doesn’t use your code for training, open source, runs locally, sends code only to the chosen AI in your browser Syntx | Doesn’t sell data, and doesn’t use your code for training, open source, confirms before performing actions Tabby | Self-hosted, code stays in your environment Augment Code | Closed source, states no training on your data, although there’s a Community plan where user data is used for training, SOC 2 Type II GoCodeo | No dedicated privacy policy or terms on homepage noted in article, generic Terms of Use, usage data wording is unclear Vibe Coder | Open source, audio is sent to Deepgram for processing and then directed to OpenAI, covered by Deepgram privacy policy, there’s no separate Vibe Coder privacy policy ## Closing thoughts So hopefully now I have given you some new tools to explore and maybe even to use in production, who knows. I tried to make this post as neutral as possible, although, as you might have noticed, whenever I saw providers without clear privacy policies and terms of use, I tend to be negative about those providers, because it is important for me to know what happens with our data, especially for production. If there’s anything in this article that you disagree with or if you find any mistakes, please let me know, because it’s important for me to know how I can improve my posts. --- If you try any of these tools, please let me know how your experience was! --- That’s all for now, see you 😌 [Launch apps with a single click 👉](https://diploi.com/)✨ --- ## References ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Hi from Diploi 🎉 > Welcome to the very first post about Diploi. We're on a journey to make software development feel... Marcus February 7, 2024 [Read on Dev.to](https://dev.to/diploi/hi-from-diploi-52j9) Welcome to the very first post about [Diploi](https://diploi.com). We're on a journey to make software development feel like magic 🪄 and we very much want you to join the ride. ## So what's Diploi? For starters, it's possibly the most fun and easy way to try out new tech stacks. With just a few clicks you can launch, for example, NextJS/Svelte or Astro + PostgreSQL and start coding right away. But it is so much more. Officially, we describe it as a _"SaaS service for managing, developing and hosting your full application"_, but really, think of it as a way to develop and run your application, all the way from initial experiments to a full service with a large team of developers, having CI/CD and running test, staging and production versions. All without any DevOps at all 🤯. In more technical terms, it could be described as a way of automating Kubernetes, as Diploi is based on Kubernetes. But if you run our ready templates you don't even need to know how to spell Kubernetes. And because we are using Kubernetes you won't be locked into Diploi forever, you can eject ⏏️ and run your solution on some other Kubernetes platform. But you might regret it 😉. ## Remote Development When developing in Diploi you install nothing on your local machine. Just connect with your editor (eg. VSCode) and get going. Nothing to set up, just code away. ## Try it out It's early days and we are working hard on adding features and growing the number of supported stacks. We'd love it if you want to try it out (and you can try it for free). Please let us know if support for your favourite framework or tech is missing. Thanks for tuning in, head out to [Diploi.com](https://diploi.com) and press **Sign up**, you won't regret it. ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # The easiest way to start new Django and Hono apps, literally one click > Discover how to spin up apps in seconds using Diploi with Hono and Django Javier June 26, 2025 Updated October 28, 2025 ###### Hono and Django now available on Diploi There are two powerful new additions to Diploi, **Hono** and **Django**! These frameworks are now officially supported, meaning you can deploy, host, and manage full applications with Hono or/and Django with one click **TLDR?** Sure, to launch a **Hono** app, go to and for **Django** apps, go to --- ## What is Hono? From their [docs](https://hono.dev/docs/), > is a small, simple, and ultrafast web framework built on Web Standards. It works on any JavaScript runtime: Cloudflare Workers, Fastly Compute, Deno, Bun, Vercel, Netlify, AWS Lambda, Lambda\@Edge, and Node.js. Hono is mainly used for backend applications, like APIs, proxy servers, edge apps, and typical servers, but that’s not all, it can also serve HTML and UI components, so it is appropiate to think of Hono as a fullstack framework. You can think of Hono as a modern alternative to Express, which supports Typescript and can be used with the most popular runtimes available Hono aims to make your life easier by enabling API Spec and type inference via Hono’s RPC, which transforms how you can share types and API expected responses between server and client, into a smooth experience. Additionally, Hono has multiple helpers and middlewares to handle typical operations, like managing Cookies, JWT, Webhooks, authentication, and headers, so you don’t need external libraries to handle these actions To launch a Hono app instantly, check out this link --- ## What is Django? From their [homepage](https://www.djangoproject.com/), > Django is a high-level Python web framework that encourages rapid development and clean, pragmatic design. Built by experienced developers, it takes care of much of the hassle of web development, so you can focus on writing your app without needing to reinvent the wheel. It’s free and open source. In simpler terms, Django is a framework for building web applications, and it is mostly considered a backend framework because it features ORM, auth, middleware, and other typical backend features, but it can also serve HTML and handle frontend templating just like fullstack frameworks, so it is fair to think that Django is whatever you need it to be 😅 Django uses a pattern they call Model-View-Template (MVT), which is similar to Model-View-Controller (MVC), with their main difference being that in MVT, the View and Controller from MVC are technically bundled together into the View from MVT Fun fact: Before this blog, I didn’t know that Django has been around since 2005… damn 🫡 Start a new Django application with Diploi, here --- ## Using Django and Hono with other frameworks in Diploi If you would like to test out how these frameworks work together with other frameworks, you can use Diploi to create monorepo applications, where you can for example, have Django as your backend and Astro in the frontend, or Hono as your API server with a Next.js fullstack app, or any other combination of frameworks and databases that fits your requirements 1. Visit the **Stack Builder** on the Diploi homepage at 1. Select all the components and add-ons 1. That’s it, click `Launch Stack` Diploi will then start a remote development environment that allows you to code in the browser and your application is deployed online. If you would like to start your application with a GitHub repository, all you need to do is register using GitHub and you will be able to start a new repository with your new application --- What frameworks should we support next? Let me know in the comments! --- You can start new apps on [Diploi for free without registration](https://diploi.com/) and if you sign up, you will get 50€ in free credits --- **References:** - - - ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Hosting a Ghost blog in seconds on Diploi, with support for custom development > Learn how to create blogs and websites with Ghost using Diploi Javier August 27, 2025 Updated October 28, 2025 ###### Launching a Ghost blog using Diploi to customize and host it If you’re interested in self-hosting open-source services, this guide will be useful for you. Diploi gets you from zero to a live blog in seconds, and the best part is that you can also customize your Ghost blogs at the code level, without the need to run anything locally using Diploi’s remote development capabilities. Let’s get straight to it! --- ## Table of contents - [What you’ll need](#what-youll-need) - [Creating a blog with Ghost](#creating-a-blog-with-ghost) - [Ship your Ghost blog to Production](#ship-your-ghost-blog-to-production) - [Set up a custom domain for your Ghost site](#set-up-a-custom-domain-for-your-ghost-site) - [New to Ghost? Try it in the cloud first for free](#new-to-ghost-try-it-in-the-cloud-first-for-free) - [References](#references) --- ## What you’ll need - A GitHub account. If you don’t have one yet, sign up here: --- ## Creating a blog with Ghost 1. **Sign up** for Diploi at `https://console.diploi.com/` using your GitHub account. 1. In your dashboard, click **Create Project +** 1. Under **Pick Components**, choose **Ghost**\ If you want to expand your Ghost blog with other tools, like a backend framework to add an API, in this section, you can add them. They will all be hosted on a single server, reducing costs and complexity. 1. In **Pick Add-ons**, select any databases or tools you want to include. 1. In **Repository**, choose **Create Repository** which will generate a new GitHub repo for you. 1. Click **Launch Stack** Diploi provisions a full cloud dev environment where you can: - Preview your Ghost site instantly - Work in the browser IDE, **or** connect over SSH with your favorite editor (VS Code, Cursor, etc.) --- ## Ship your Ghost blog to Production Once you are ready to create and launch your blog to production, you can create a new deployment, ready to receive your users: 1. Open your project’s dashboard:\ `https://console.diploi.com//project/` 1. Click **Create Deployment +** 1. Choose **Production** as the stage 1. Pick a **cluster size** that fits your needs 1. Select the **source branch** to deploy (eg. `main`) 1. Add any necessary **environment variables** 1. Click **Create Deployment +** That’s it, your Ghost blog is deployed and ready to scale. To access the admin panel, you must add to your Ghost URL the slug `/ghost`, where you can setup your password and then access your site’s dashboard. Example: `example.com/ghost` --- ## Set up a custom domain for your Ghost site By default, you’ll get a `.diploi.me` URL. To use your own domain: 1. Go to your Production deployment’s **Options** tab:\ `https://console.diploi.com//project//deployment//options` 1. In **Endpoints**, disable **Use Auto-Generated Endpoints** 1. You’ll see your current subdomain and a **Use custom domain** checkbox 1. Enable it and enter your domain (eg. `example.com`) 1. Scroll down and **Save Changes** 1. In your DNS provider, create a **CNAME** record pointing your domain to **edge.diploi.com** Allow up to \~30 minutes for DNS and SSL to propagate. --- ## New to Ghost? Try it in the cloud first for free You don’t need a local setup to explore Ghost on Diploi: - **No account yet?**\ Use the **Stack Builder** to spin up a temporary environment and test the workflow without registering for an account and for free. - **Already signed in?**\ Create a new project and select **Quick Launch** in the **Repository** section to start experimenting without wiring up a new repository. --- What other open source tools would you like us to support? Let us know on [Discord](https://discord.gg/vvgQxVjC8G), we are looking forward to hearing more ideas that could help us improve! 🤗 --- ## References - Ghost Docs - Diploi Components - Diploi Ghost Component (GitHub) - Custom Domains ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Create Astro apps quickly, from Development to Production on Diploi > Bring the versatility of platforms like Heroku to your Astro development workflow Javier August 26, 2025 Updated October 28, 2025 ###### Getting started with Astro apps, the easy way You can start an Astro project in several ways, by using the official CLI, grabbing a community starter from GitHub, or wiring up your own config, but if you’re looking for the **fastest and smoothest way**, Diploi makes it ridiculously easy. --- ## Table of contents - [What you need](#what-you-need) - [How to create an app with Astro](#how-to-create-an-app-with-astro) - [Launching your Astro app to Production](#launching-your-astro-app-to-production) - [Configuring a custom domain for your Astro site in Production](#configuring-a-custom-domain-for-your-astro-site-in-production) - [Trying out Astro for the first time?](#trying-out-astro-for-the-first-time) - [References](#references) --- ## What you need - A GitHub account, sign up here if you don’t have one yet: --- ## How to create an app with Astro 1. **Sign up** for a free Diploi account at 1. In the Dashboard, click **Create Project +** 1. Under **Pick Components**, choose **Astro** You can also add additional tools or services here if you want to extend your stack. 1. In **Pick Add-ons**, select any databases or extra tools you need. 1. Choose **Create Repository** so Diploi generates a brand new GitHub repo for your project. 1. Click **Launch Stack** Diploi will spin up a full Development environment in the cloud where you can: - Preview your Astro site live instantly - Code directly in the browser using the built-in IDE - Or connect remotely via SSH using VS Code, Cursor, or any dev container-friendly IDE --- ## Launching your Astro app to Production When you’re ready to go live: 1. Open your Astro Project’s dashboard: `https://console.diploi.com//project/` 1. Click **Create Deployment +** 1. Select **Production** as the deployment stage 1. Choose the **cluster size** depending on your needs 1. Pick the **source branch** you want to deploy, such as `main` 1. Customize any necessary **environment variables** 1. Click **Create Deployment +** Your Astro site is now fully deployed and ready to scale! --- ## Configuring a custom domain for your Astro site in Production By default, your site will use a `.diploi.me` URL. To switch to a custom domain: 1. Head to your Production Deployment’s **Options** tab, or go directly to: `https://console.diploi.com//project//deployment//options` 1. In the **Endpoints** section, click to disable **Use Auto‑Generated Endpoints** 1. A field will appear showing your current Diploi subdomain, and a checkbox to enable a custom domain 1. Enable the checkbox and enter your custom domain name 1. Scroll down and click **Save Changes** 1. In your DNS settings, create a **CNAME** record pointing to **edge.diploi.com** Give it up to 30 minutes for DNS and SSL propagation to complete. --- ## Trying out Astro for the first time? You don’t need to install anything, just try Astro in the cloud on Diploi in two simple ways: - **Not signed up yet?** Head to to launch a trial project, or go straight to the Astro component page: - **Already have a Diploi account?** Create a new project and in the **Repository** section, select **Quick Launch**. This gives you a temporary environment to explore Astro without connecting a repo. --- Want to see other frameworks supported on Diploi? Let us know on [Discord](https://discord.gg/vvgQxVjC8G)! --- Sign up at [Diploi](https://diploi.com/) and get **50 € in free credits**. --- ## References - - ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Starting a new Bun app on Diploi > Explore how to create new Bun applications readily online, without any server config Javier August 25, 2025 Updated October 28, 2025 ###### Getting started with Bun on Diploi There are thousands of tutorials going over how to create a Bun app and then host it online. This is not that 😎 In this tutorial, we will show you how to completely skip any DevOps work that you usually need to put your apps online by using Diploi, so that you can create Bun applications that can be launched to production in seconds. And yes, I’m not exaggerating. --- ## Table of contents - [What you need](#what-you-need) - [How to create an app with Bun](#how-to-create-an-app-with-bun) - [Launching your Bun app to Production](#launching-your-bun-app-to-production) - [Configuring a custom domain for your Bun app in Production](#configuring-a-custom-domain-for-your-bun-app-in-production) - [Trying out Bun for the first time?](#trying-out-bun-for-the-first-time) - [References](#references) --- ## What you need - A **GitHub account**, sign up here if you don’t have one yet, - A **Diploi account**, sign up for a free Diploi account at --- ## How to create an app with Bun 1. In the Dashboard, click **Create Project +** 1. Under **Pick Components**, choose **Bun** You can add other frameworks from this page if you want to create a monorepo application, eg, Bun for API + React for frontend. 1. In **Pick Add-ons**, select any databases you need. 1. Choose **Create Repository**, which will generate a new GitHub repo. 1. Finally, click **Launch Stack** This will create a new Project using Bun, which will also start a new Development environment for your Bun app. You will be able to preview your Bun online, customize its URL, and even start coding in the browser using our built-in IDE, or by connecting remotely with SSH, using VS Code, Cursor, or any dev container-friendly IDE to start coding remotely from your desktop, without having to install anything locally. --- ## Launching your Bun app to Production Once your Bun app is ready for Production, follow these steps to launch it: 1. Open your Bun Project’s dashboard: `https://console.diploi.com//project/` 1. Click **Create Deployment +** 1. Select **Production** as the deployment stage 1. Choose the **cluster size** depending on your needs 1. Pick the **source branch** you want to deploy from, such as `main` 1. Customize any necessary **environment variables** 1. Click **Create Deployment +** This will create a new Production deployment for your Bun app. --- ## Configuring a custom domain for your Bun app in Production By default, all applications built on Diploi use a `.diploi.me` URL. You can customize the subdomain, eg, `foo.diploi.me` to `foobar.diploi.me`, but if you want to switch to a fully custom domain, this is what you need to do: 1. Head to your Production Deployment’s **Options** tab, or go directly to: `https://console.diploi.com//project//deployment//options` 1. In the **Endpoints** section, click to disable **Use Auto‑Generated Endpoints** 1. A field will appear showing your current Diploi subdomain, and a checkbox to enable a custom domain 1. Enable the checkbox and enter your custom domain name 1. Scroll down and click **Save Changes** 1. In your DNS settings, create a **CNAME** record pointing to **edge.diploi.com** This change is usually instant, but it can take up to 30 minutes for DNS and SSL propagation to be completed. --- ## Trying out Bun for the first time? Supposing you haven’t ever used Bun, here’s how to try it out without even running an `npm` command: - Option 1: **Starting a trial without registering an account** Go to to launch a trial project, or visit the Next.js component page - Option 2: **Starting a Quick Launch if you have an account on Diploi** Create a new project and in the **Repository** section, select **Quick Launch**. This gives you a temporary environment to explore Bun without connecting a repo. --- What else should we add to Diploi? Message us on [Discord](https://discord.gg/vvgQxVjC8G)! --- Sign up at [Diploi](https://diploi.com/) and get **50 € in free credits**. --- ## References - - ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Deploying Deno Applications in Easy Mode > How to use Diploi to host and develop Deno-powered apps without configuring servers Javier September 22, 2025 Updated October 28, 2025 ###### Ship new Deno apps using Diploi with zero server configuration Deno is runtime, created to be the successor to Node.js, even created by the creator of Node!. It comes with native TypeScript support, and meant for building web servers and backend applications. In this guide, you’ll learn how to launch a vanilla Deno application on Diploi and get it live online in seconds. You won’t have to handle YAML configs or setup servers manually, Diploi handles all that for you. We’ll walk through everything from creating your Deno project on Diploi, to pushing it to production, and even setting up a custom domain. Let’s go! --- ## Table of contents - [Getting started with Deno on Diploi](#getting-started-with-deno-on-diploi) - [Launching your Deno app to Production](#launching-your-deno-app-to-production) - [Configuring a custom domain for your Deno app](#configuring-a-custom-domain-for-your-deno-app) - [Trying out Deno for the first time?](#trying-out-deno-for-the-first-time) - [References](#references) --- ## Getting started with Deno on Diploi ### What you need To follow along, make sure you have: - A GitHub account. - A Diploi account. That’s pretty much it. If you don’t have Diploi account, you can create one for free, no payment method required. ### How to create an app with Deno Once you have sign-in, follow these steps: - Create a new project, by clicking the “Create Project +” button on your Dashboard. - Pick Deno as the component: Under Pick Components, choose the Deno option. (Diploi might list Deno as a runtime or framework option.) If you want to go full-stack, you can add another component here too, for example, you could combine a Deno backend API with a React front-end in a single project. - Select any add-ons (optional): In Pick Add-ons, you can attach databases or other services if your app needs them (like PostgreSQL, Redis, etc.), or you can skip this for now. - Create a repository: Choose Create Repository so Diploi will generate a new GitHub repository for your project’s code. Give your project a name and confirm the creation, Diploi will set up the repo with a basic Deno starter for you. - Launch the stack: Finally, click Launch Stack. Diploi will now provision your new Deno app environment. And that should be it, in a few moments, you’ll have a fresh Deno project running on Diploi. In the background, Diploi spins up all the necessary infrastructure (containers, runtime, etc.) to run your Deno app on a publicly reachable, SSL-protected URL. By default, every new project starts in a **Remote Development deployment**, similar to GitHub Codespaces, where you can code right away, without running the app locally. You have tow options to start developing your new Deno app using this Remote Development environment: - By opening the browser-based IDE, and edit your code there. - Or by connecting your local code editor (such as VS Code or Cursor) to the remote environment via SSH. This way you can code remotely as if it were running on your own machine. Either way, there’s no need to git clone the repo or run deno install locally, everything is already set up in the cloud environment. Diploi will live-reload or rebuild as needed so you can preview your Deno app’s endpoints instantly. --- ## Launching your Deno app to Production Once you’ve been developing and you’re happy with your Deno application, you can deploy it to a production environment. - Open your project’s page: In the Diploi console, go to your Deno project’s dashboard. (The URL will look like: \/project/\). - Create a new deployment: Click the “Create Deployment +” button. - Choose Production stage: Select Production as the deployment stage when prompted. - Select a cluster size: Pick the cluster size or plan that fits your needs (you can start small for testing, and scale up later if needed). - Pick the source branch: Choose which Git branch to deploy, for example “prod”. - Set environment variables (if any): Add or adjust any environment variables your Deno app might require in production. For a basic app, you might not need to change anything here. - Launch the deployment: Click Create Deployment to spin up the production instance of your app. Give Diploi a moment to work its magic. It will build a production-ready version of your Deno application and deploy it. That’s all it takes, and your Deno app is now live in Production! You should see it running on a public URL (by default, on a Diploi subdomain). Now let’s customize that URL to use your own domain name. --- ## Configuring a custom domain for your Deno app By default, Diploi gives your production deployment a random subdomain ending in `.diploi.me` and SSL protection. For example, your app might be accessible at my-app.diploi.me. While that works out of the box, you’ll probably want to use your own domain for a real project. Here’s how to set that up: - Open the Options tab: Navigate to the Options settings for your Production deployment. You can find this in your deployment’s dashboard (there’s an “Options” tab), or go directly to the URL: \/project/\/deployment/\/options. - Disable the auto-generated domain: Scroll to the Endpoints section. There, flip the toggle off for Use Auto-Generated Endpoints. This tells Diploi you want to use a custom domain instead of the default `.diploi.me` address. - Enter your custom domain: Once you disable the auto-endpoint, a field will appear showing the current Diploi subdomain and an option to enter a custom domain. Check the box for Use custom domain, then type in the custom domain you want to use (for example, `yourdomain.com`). - Save changes: Scroll down and click Save Changes to apply the new domain configuration. Diploi will update your deployment to recognize the custom domain. - Update your DNS record: Finally, go to your domain provider and create a CNAME record for your chosen domain or subdomain, and point that CNAME record to `edge.diploi.com`. Your app will now be accessible via the newly setup domain you entered. The DNS change often propagates quickly, but it can take up to \~30 minutes to work. --- ## Trying out Deno for the first time? If you are curious about Deno, but not ready to commit to a full project setup? Then you can spin up a temporary Deno instance in Diploi to play around. Here are two easy ways to try Deno on Diploi: - Option 1 - Start a trial without an account: Head to the Diploi StackBuilder to launch a free trial project instantly. This lets you create a temporal Deno environment. Just select the Deno stack (along with any extras you want) and click Launch, no account or credit card required. - Option 2 - Quick Launch with a Diploi account: If you already have a Diploi account and are logged in, you can use the Quick Launch feature. Create a new project as usual, and in the Repository section, choose Quick Launch instead of linking a GitHub repo. This will spin up a Deno project environment for you to experiment with, without creating a permanent repository. Now you know how to go from zero to a deployed Deno app using Diploi, without dealing with servers, build tooling, or DevOps. --- We hope this guide helps you get your Deno application online faster and easier than ever. If you have any questions or want to share what you’re building, feel free to join our community on Discord and say hello. --- ## References - Official Deno Documentation - Deno in Diploi - Diploi Components - Custom Domains ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # The best way to start new Django apps and host them online > Use Django on Diploi to skip server config and focus only on the code, no DevOps Javier August 24, 2025 Updated October 28, 2025 ###### Getting started with Django on Diploi Django is a huge part of the web, and there are many options for getting a Django app online, but Diploi might be the easiest one out there. In this guide, I’ll walk you through spinning up a brand-new Django app on Diploi, which will be live on the internet from the moment you create it. No YAML files or boring server setup screens, just code and go. --- ## Table of contents - [What you need](#what-you-need) - [How to create an app with Django](#how-to-create-an-app-with-django) - [Launching your Django app to Production](#launching-your-django-app-to-production) - [Configuring a custom domain for your Django app in Production](#configuring-a-custom-domain-for-your-django-app-in-production) - [Trying out Django for the first time?](#trying-out-django-for-the-first-time) - [References](#references) --- ## What you need - A **GitHub account** - - A **Diploi account** - --- ## How to create an app with Django 1. In the Dashboard, click **Create Project +** 1. Under **Pick Components**, choose **Django** 1. In **Pick Add-ons**, you can add one or multiple databases to your app 1. Choose **Create Repository**, which will generate a new GitHub repo 1. Now click **Launch Stack** That’s it! This process has now created a new Project with Django. By default, all new Projects on Diploi start with a fresh Development deployment. In Diploi, we use Kubernetes to generate the deployment’s infrastructure, which consists of a core, but for simplicity, you can think of a deployment as being the same as a virtual machine. The Development deployment that was just created represents a VM that is hosting your Django app, which is exposing your app online with an SSL-protected URL. Additionally, you can skip configuring anything locally to start coding on your new Django app by using Diploi’s browser IDE, or if you prefer to use your local IDE, you can connect to the remote development environment directly, without `git clone` or `pip install` on your local machine. --- ## Launching your Django app to Production Once your app is ready for Production, from Diploi, you can launch new deployments easily, without server config work. Here’s how: 1. Open your Django Project’s dashboard: `https://console.diploi.com//project/` 1. Click **Create Deployment +** 1. Select **Production** as the deployment stage 1. Choose the **cluster size** depending on your needs 1. Select the **source branch** you want to deploy from, such as `main` 1. Customize any necessary **environment variables** 1. Click **Create Deployment +** This will create a new Production deployment for your Django app, ready to serve users. --- ## Configuring a custom domain for your Django app in Production Any deployment created will be launched with a generic SSL-protected `.diploi.me` URL to expose your app online, but probably you would like to use a custom domain instead. To add a custom domain, do the following: 1. Navigate to the **Options** tab of the Deployment you want to assign a custom domain to. The URL should look like this: `https://console.diploi.com//project//deployment//options` 1. Once you are in the **Options** tab, scroll down to the **Endpoints** section and disable the **Use Auto‑Generated Endpoints** option 1. An input field will now appear showing your current deployment’s subdomain, and below it, you will notice a checkbox labeled **Use custom domain**. Enable the checkbox, and now you can enter the new custom domain name you want to use 1. Once you are done, scroll down on the page and click **Save Changes**56. In the DNS settings for your Domain, you need to create a new **CNAME** record pointing to **edge.diploi.com** When you use a custom domain, the update usually happens instantly, but it can take up to 30 minutes for DNS and SSL propagation to be completed. --- ## Trying out Django for the first time? In case this is your first time exploring Django and how it works, you might want to skip any config work usually required to get started. With Diploi, you can skip all the boring config work and jump straight to test-drive Django without having to install anything locally in two ways: - Option 1 - **Starting a trial without registering an account** Go to to launch a trial project, or visit the Next.js component page - Option 2 - **Starting a Quick Launch Project if you have an account on Diploi** Create a new project and in the **Repository** section, select **Quick Launch**. This gives you a temporary environment to explore Django without connecting to a repo. --- Now you know the easiest way to launch new Django apps from start to production, without doing any DevOps work. If you would like to get involved with Diploi, join our [Discord](https://discord.gg/vvgQxVjC8G). We would like to hear from you 🙂‍↕️ --- Sign up [Diploi](https://console.diploi.com/) for free and receive **50 € in free credits**. --- ## References - - ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # FastAPI on Diploi: Code, preview, and ship without DevOps > Start a FastAPI service with remote development, live previews, and one-click production, without configuring SSL certificates or manual server config. Javier September 22, 2025 Updated October 28, 2025 ###### Spin up FastAPI on Diploi with zero server configuration FastAPI is a high-performance Python framework designed for APIs. It uses type hints, supports async out of the box, and auto-generates OpenAPI docs, which makes it ideal for both prototypes and production services. In this guide, we’ll start from a simple FastAPI project and have it running on Diploi in minutes. Diploi handles the build, configuration, and runtime for you. We’ll create your FastAPI project in Diploi, promote it to production, and then connect a custom domain. Let’s get started. --- ## Table of contents - [Getting started with FastAPI on Diploi](#getting-started-with-fastapi-on-diploi) - [Launching your FastAPI app to Production](#launching-fastapi-to-production) - [Configuring a custom domain for your FastAPI app](#using-a-custom-domain-with-your-fastapi-app) - [Trying out FastAPI for the first time?](#just-exploring-fastapi) - [References](#references) --- ## Getting started with FastAPI on Diploi ### What you need To follow along, you’ll need: - A GitHub account - A Diploi account You can create a Diploi account for free, no credit card required. ### How to create a FastAPI app Now, to get started, you’ll need to create a Project using FastAPI, this is how: - Create a new project: Once you sign-in, you should land in the Project creation page, but in case this is not your first time using Diploi, access your Dashboard and click the **Create Project +** button. - Choose the FastAPI component: In **Pick Components**, select **FastAPI** (you may find it under Python/FastAPI). If you want a full-stack setup, add a frontend too, e.g., pair a FastAPI backend with a React UI in the same project. - Add optional services: In **Pick Add-ons**, attach databases or caches if needed (PostgreSQL, Redis, etc.). You can skip this now and add them later by editing the `diploi.yaml` at the project root. - Create a repository: Choose **Create Repository**, so Diploi can scaffold a new GitHub repo for your app. - Launch the stack: Click **Launch Stack**, and Diploi will provision the environment and boot your FastAPI app. By launching your stack, Diploi will setup your app’s folder structure as a monorepository, which will be accessible online with a public URL, and it will also start a **Remote Development** environment, so you can start coding without the need of cloning the repository locally. You can access the Remote Development environment via: - The browser IDE, - Or your local editor by connecting by SSH. You can still develop locally if you prefer to run your application in your own environment, so you are not constrained to the Remote Development environment to create your application. --- ## Launching FastAPI to Production When your FastAPI application is ready to go live in a production environment, follow these steps: - Push your changes to GitHub: We recommend separate branches per stage of your app (e.g., Git Flow). - Open your project dashboard: In the Diploi console, navigate to your FastAPI project’s page. - Create a new deployment: Click **Create Deployment +** and choose **Production** for the stage. - Choose a cluster size: Select the resources that match your needs. We recommend that you start small, and scale later. - Select the source branch: Pick the Git branch to deploy (e.g., `main` or `prod`). - Configure environment variables: Add any variables that your API will need in production. - Launch the deployment: Click **Create Deployment** to start up the production deployment. Diploi will build and deploy a production-ready environment. Now, let’s add a custom domain. --- ## Using a custom domain with your FastAPI app As you might have noticed, Diploi gives your deployments a random `.diploi.me` subdomain. For example, your service might be reachable at `my-app.diploi.me`. To use your own domain: - Open the Options tab: In your Production deployment, go to the **Options** tab from the deployment dashboard. - Turn off generated endpoints: In **Endpoints**, disable **Use Auto-Generated Endpoints** to reveal the custom domain settings. - Add your hostname: Enable **Use Custom Domain** and enter the domain you will use, for example `api.yourdomain.com` or `yourdomain.com`. - Save the configuration: Scroll to the bottom and click **Save Changes**. - Configure your domain’s DNS settings: From your domain provider, you must create a new DNS **CNAME** record for the hostname you chose and point it to `edge.diploi.com`. Once you modify your DNS settings, the update can take up to 30 minutes to propagate, but usually it is nearly instant. Your FastAPI application will be available at your custom domain and SSL-protected automatically. --- ## Just exploring FastAPI? You can try FastAPI on Diploi in seconds without even registering an account. Here are two quick options to launch a playground to test-drive FastAPI: - Option 1 - Launch a trial without signing up Open the Diploi StackBuilder and start a free trial project. Pick the **FastAPI** stack and click **Launch**. No account or credit card required and you get a temporary environment to explore. - Option 2 - Quick Launch with your Diploi account If you are logged in, create a new project and in the **Repository** section, choose **Quick Launch** instead of creating a GitHub repository. Diploi provisions a ready-to-use FastAPI app so you can experiment immediately. These options are great for testing and learning. For production, create a full project and repository. Remember FastAPI exposes interactive docs at `/docs` out of the box. --- And that’s it! Now you should have a fresh deployment with FastAPI running. If you have questions, reach out on Discord or via email by messaging us at Happy coding 👩‍💻 --- ## References - Official FastAPI Documentation - FastAPI in Diploi - Diploi Components - Custom Domains ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Deploying Flask Apps the Easy Way > Use Diploi to run and iterate on Flask without touching servers Javier September 22, 2025 Updated October 28, 2025 ###### Launch new Flask apps on Diploi with zero server setup Flask is a lightweight Python framework for building web APIs and full-stack apps. It’s minimal by design, easy to extend, and great for everything from quick prototypes to production services. In this guide, we’ll take a Flask project and get it running on Diploi instantly. You won’t need to write YAML or provision machines. Diploi builds, configures, and runs it for you. We’ll go from creating your Flask project in Diploi, to launching it to production, and finally adding a custom domain. Let’s begin. --- ## Table of contents - [Getting started with Flask on Diploi](#getting-started-with-flask-on-diploi) - [Launching your Flask app to Production](#launching-your-flask-app-to-production) - [Configuring a custom domain for your Flask app](#configuring-a-custom-domain-for-your-flask-app) - [Trying out Flask for the first time?](#new-to-flask) - [References](#references) --- ## Getting started with Flask on Diploi ### What you need To follow along, you’ll need: - A GitHub account - A Diploi account That’s it. If you don’t have a Diploi account yet, you can create one for free, no credit card required. ### How to create a Flask app After signing in, do the following: - Create a new project: Click the **Create Project +** button on your Dashboard. - Choose Flask as the component: In **Pick Components**, select **Flask** (it may appear under Python/Flask). If you want a full-stack setup, add a frontend component here too, for example, pair a Flask API with a React UI in the same project. - Add optional services: In **Pick Add-ons**, attach databases or caches if you need them (PostgreSQL, Redis, etc.). You can skip this for now and add them later by modifying the `diploi.yaml` file in the root of the project. - Create a repository: Select **Create Repository** so Diploi can generate a new GitHub repo for your code. Name the project and confirm, Diploi will scaffold a minimal Flask starter for you. - Launch the stack: Click **Launch Stack**. Diploi will provision the environment and boot your Flask app. In a minute or two, you’ll have a fresh Flask project running on Diploi with a public URL and SSL-protected. Behind the scenes, Diploi handles a Kubernetes cluster and networking for you. By default, new projects start with a **Remote Development** workspace, so you can code immediately, without having to clone your repository locally. You can start using the Remote Development environment in two ways: - Open the browser IDE and edit files right there. - Or connect your local editor (e.g., VS Code or Cursor) over SSH to the remote environment, so it feels like coding on your own machine. Either way, there’s no need to clone the repo or set up Python, virtualenv, or `pip` locally. The environment is already configured in the cloud. Diploi will hot-reload or restart the app as needed so you can preview changes instantly. --- ## Launching your Flask app to Production When you’re happy with your Flask app and it’s time to promote it to a production environment, do the following: - Push your changes to GitHub: We recommend you use different branches for each stage of your application, a popular strategy is Git Flow. - Open your project dashboard: In the Diploi console, navigate to your Flask project’s page. - Create a new deployment: Click **Create Deployment +** and the select **Production** for the stage. - Choose a cluster size: Select the plan/resources that fit your needs (you can start small and scale later). - Select the source branch: Pick the Git branch to deploy (e.g., `main` or `prod`). - Configure environment variables (if needed): Add any variables your app requires in production. - Launch the deployment: Click **Create Deployment** to spin up the production instance. Diploi then builds your app for production and deploys. Your Flask app is now live in Production. Next, let’s point your own domain to it. --- ## Configuring a custom domain for your Flask app By default, Diploi assigns your production deployment a random `.diploi.me` subdomain with HTTPS. For example, your app might be available at `my-app.diploi.me`. If you want to use your own domain, follow these steps: - Open the Options tab: In your Production deployment, go to the **Options** tab from the deployment dashboard. - Disable generated endpoints: In the **Endpoints** section, switch off **Use Auto-Generated Endpoints** to enable custom domain settings. - Enter your domain: Check **Use custom domain** and type the hostname you want to use, for example `yourdomain.com`. - Save the changes: Scroll to the bottom of the page, and then click **Save Changes** to apply the configuration. Diploi will update the deployment settings. - Point DNS: In your DNS provider, create a **CNAME** record for the chosen hostname and point it to `edge.diploi.com`. After the DNS settings propagate, your Flask app be accessible using your custom domain. SSL certificates are issued automatically once the domain resolves to Diploi. The updates can happen quickly, but sometimes it can take up to about 30 minutes. --- ## New to Flask? You can spin up a temporary Flask environment on Diploi and explore what’s possible within minutes. Here are two quick ways to test-drive Flask on Diploi: - Option 1 - Launch a trial without signing up Open the Diploi StackBuilder and start a free trial project. Pick the **Flask** stack (plus any extras you want) and hit **Launch**. No account, no credit card, just a disposable Flask environment you can poke around in. - Option 2 - Quick Launch with your Diploi account If you’re logged in, create a new project as usual and, in the **Repository** step, choose **Quick Launch** instead of linking GitHub. Diploi will provision a ready-to-use Flask app so you can experiment immediately, no permanent repo until you decide to create one. With that, you can go from zero to a deployed Flask service on Diploi, although keep in mind that these options are not meant for production apps, they are only for testing. --- We hope this guide helps you get your Flask app online faster. If you have questions or want to share what you’re building, join our Discord community and say hello. --- ## References - Official Flask Documentation - Flask in Diploi - Diploi Components - Custom Domains ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # How to create Hono apps that are ready for Production using Diploi > Make your Hono development as seamless as deploying on Heroku Javier August 23, 2025 Updated October 28, 2025 ###### Getting started with Hono, but in easy-mode You probably know how to start a new Hono app just using `npm create hono@latest`, for example, but this guide is not about that. Here we’ll show you how to get your new Hono app online in record time. --- ## Table of contents - [What you need](#what-you-need) - [How to create an app with Hono](#how-to-create-an-app-with-hono) - [Launching your Hono app to Production](#launching-your-hono-app-to-production) - [Configuring a custom domain for your Hono app in Production](#configuring-a-custom-domain-for-your-hono-app-in-production) - [Trying out Hono for the first time?](#trying-out-hono-for-the-first-time) - [References](#references) --- ## What you need - A GitHub account, sign up here if you don’t have one yet: - A Diploi account, sign up for a free Diploi account at --- ## How to create an app with Hono 1. **Sign up** for a free Diploi account at 1. In the Dashboard, click **Create Project +** 1. Under **Pick Components**, choose **Hono** You can add other frameworks from this page. 1. In **Pick Add-ons**, select any databases or extra tools you need. 1. Choose **Create Repository** so Diploi generates a new GitHub repo for your project. 1. Click **Launch Stack** Diploi then starts a Development environment for your new Hono app, from which you can: - Preview your Hono endpoints live instantly - Code directly in the browser using the built-in IDE - Or connect remotely via SSH using VS Code, Cursor, or any dev container-friendly IDE --- ## Launching your Hono app to Production When your Hono app is ready for Production, follow these steps to start a Production deployment: 1. Open your Hono Project’s dashboard: `https://console.diploi.com//project/` 1. Click **Create Deployment +** 1. Select **Production** as the deployment stage 1. Choose the **cluster size** depending on your needs 1. Pick the **source branch** you want to deploy from, such as `main` 1. Customize any necessary **environment variables** 1. Click **Create Deployment +** Your Hono app will now be deployed in Production mode! --- ## Configuring a custom domain for your Hono app in Production By default, your app will use a `.diploi.me` URL, for which you can customize its subdomain, but if you want to switch to a fully custom domain: 1. Head to your Production Deployment’s **Options** tab, or go directly to: `https://console.diploi.com//project//deployment//options` 1. In the **Endpoints** section, click to disable **Use Auto‑Generated Endpoints** 1. A field will appear showing your current Diploi subdomain, and a checkbox to enable a custom domain 1. Enable the checkbox and enter your custom domain name 1. Scroll down and click **Save Changes** 1. In your DNS settings, create a **CNAME** record pointing to **edge.diploi.com** The change can be instant, but in some cases, it can take up to 30 minutes for DNS and SSL propagation to complete. --- ## Trying out Hono for the first time? You don’t want to run anything locally, and you just want to try Hono, you can do it in the cloud using Diploi in one of these two ways: - **Starting a trial without registering an account** Head to to launch a trial project, or go straight to the Hono component page: - **Starting a Quick Launch if you have an account on Diploi** Create a new project and in the **Repository** section, select **Quick Launch**. This gives you a temporary environment to explore Hono without connecting a repo. --- Want to see other frameworks supported on Diploi? Let us know on [Discord](https://discord.gg/vvgQxVjC8G)! --- Sign up at [Diploi](https://diploi.com/) and get **50 € in free credits**. --- ## References - - ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # How to create Laravel apps that are ready for Production using Diploi > In this tutorial guide we go over the process of creating and hosting an application using Laravel in Diploi Javier September 22, 2025 Updated October 28, 2025 ###### Getting started with Laravel, but in easy-mode If you are part of the PHP world, you must have heard of Laravel. A very flexible framework to build web applications with PHP, very popular around the world. You probably know how to start a new Laravel app running `composer create-project laravel/laravel`, that’s not a problem really. What it is a problem, is getting your new Laravel app online, with CI/CD and SSL-protected. In this guide, we’ll show you how to get your new Laravel app not only setup while skipping the local install, but also get it online in record time by using Diploi, all without setting up servers or manipulating YAML files. --- ## Table of contents - [What you need](#what-you-need) - [How to create an app with Laravel](#how-to-create-an-app-with-laravel) - [Launching your Laravel app to Production](#launching-your-laravel-app-to-production) - [Configuring a custom domain for your Laravel app in Production](#configuring-a-custom-domain-for-your-laravel-app-in-production) - [Trying out Laravel for the first time?](#trying-out-laravel-for-the-first-time) - [References](#references) --- ## What you need - A GitHub account - A Diploi account If you have that, you are ready. --- ## How to create an app with Laravel 1. In the Diploi Dashboard, click **Create Project +**. 1. Under **Pick Components**, choose **Laravel**. You can add other frameworks on this page too, if you want to create a multi-component app, for example, a Laravel backend with a React frontend. 1. In **Pick Add-ons**, select any databases or extra services your app needs (for example, add a MariaDB or PostgreSQL database if your Laravel app will use one). 1. In the **Repository** section, choose **Create Repository** to have Diploi generate a new GitHub repository for your project. 1. Finally, click **Launch Stack**. This process will create a new Project with Laravel, and every new project on Diploi launches with a **Remote Development** deployment. This Remote Development envrironment allows you to start coding without having to run anything locally. Diploi provides a browser-based IDE so you can code directly in your browser, or you can connect your local IDE to the remote dev environment via SSH. Under the hood, Diploi uses Kubernetes to provision the infrastructure for your app within a single cluster, so you don’t need to manage services individually. --- ## Launching your Laravel app to Production When you’re ready to take your Laravel app live in front of real users, you can easily launch a Production deployment on Diploi by following these steps: 1. Open your Laravel project’s dashboard at Diploi, the URL will look like `https://console.diploi.com//project/`. 1. Click **Create Deployment +**. 1. Select **Production** as the deployment stage. 1. Choose the cluster size for your Production deployment, depending on your needs. 1. Select the source branch you want to deploy (for example, `prod`). 1. Set any environment variables your app needs for production (e.g. database credentials, Laravel environment settings, etc.). 1. Click **Create Deployment +**. This will spin up a new **Production** deployment for your Laravel app, fully configured and ready to serve your users. --- ## Configuring a custom domain for your Laravel app in Production By default, your app will be live at a `{your-app}.diploi.me` URL (and you can customize the subdomain). But, you might want to use your own domain name for your production site. To set up a custom domain for your Laravel app: 1. Go to the **Options** tab of your Production deployment’s dashboard, you can also navigate directly to the Options URL: `https://console.diploi.com//project//deployment//options`. 1. Scroll down to the **Endpoints** section and disable the **Use Auto-Generated Endpoints** option. 1. Once you toggle that off, a field will appear showing your current Diploi subdomain, along with a checkbox to **Use custom domain**. Check that box, then enter the custom domain name you want to use for your app (e.g. `myawesomeapp.com`). 1. Click **Save Changes**. 1. Now, go to your DNS provider’s settings for your domain and create a **CNAME record** pointing your chosen domain (or subdomain) to `edge.diploi.com`. That’s it! The custom domain changes usually take effect instantly, but it can take up to 30 minutes for DNS changes and SSL certificate provisioning to propagate fully. Once it’s done, your Laravel app will be accessible at your own domain with HTTPS. --- ## Trying out Laravel for the first time? If you’re new to Laravel or just want to see it in action without setting up anything locally, Diploi gives you a couple of easy ways to test-drive Laravel in the cloud: - **Starting a trial without registering an account** Go to our homepage and the choose Laravel plus any other components you would like to try out. You can also visit - **Starting a Quick Launch with an account** If you already have a Diploi account, you can create a new project and, in the **Repository** section, select **Quick Launch**. This will give you a temporary development environment to play with Laravel, without connecting to any Git repository. Now you know the easiest way to go from “Hello World” to a production-ready Laravel app, all without any DevOps. --- What other frameworks or services would you like to see supported on Diploi? Join our [Discord](https://discord.com/invite/vvgQxVjC8G) and let us know, We would love to hear from you. --- ## References - Official Laravel Documentation - Laravel in Diploi - Diploi Components - Custom Domains ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Hosting n8n on Diploi > Spin up n8n: Build automations, preview, and ship without DevOps. Javier September 23, 2025 Updated October 28, 2025 ###### Spin up n8n on Diploi with zero server configuration n8n is an open-source workflow automation tool with a visual editor and lots of integrations. In this guide, we’ll create an instance of n8n and get it running on Diploi in minutes. Diploi handles the build, configuration, and runtime, so you can focus on your automations, and not managing infrastructure. --- ## Table of contents - [Getting started with n8n on Diploi](#getting-started-with-n8n-on-diploi) - [Launching your n8n app to Production](#launching-your-custom-nodes-for-n8n-to-production) - [Configuring a custom domain for your n8n app](#configuring-a-custom-domain-for-your-n8n-app) - [New to n8n? Try it in the cloud first for free](#new-to-n8n-try-it-in-the-cloud-first-for-free) - [References](#references) --- ## Getting started with n8n on Diploi ### What you need - A GitHub account - A Diploi account You can create a Diploi account for free, no credit card required. ### How to get n8n hosted online After signing in: - **Create a new project:** Click **Create Project +** on your Dashboard. - **Pick the n8n component:** In **Pick Components**, select **n8n** (look under Automation/Tools). Want a bundle? Add more components (e.g., a frontend) and run them together. - **Optional add-ons:** By default, n8n will launch with PostgreSQL, but you can attach other databases or caches if needed. - **Create a repository:** Choose **Create Repository** so Diploi scaffolds a new GitHub repo for your app. - **Launch the stack:** Click **Launch Stack**. Diploi provisions your environment and starts n8n. Once you are done and your environment finishes loading, you’ll be able to access your n8n instance. Diploi sets up a **Remote Development** environment with a public preview URL, so you can start right away, without requiring a local setup. Which you can use via: - **Browser IDE**: Edit files online with a full VS Code-style experience. - **Your local editor via SSH**: Connect VS Code, Cursor, or any SSH-friendly IDE to the remote dev container. This is ideal if you want to create your own custom nodes. For more about custom nodes, check the official guide from the n8n team: --- ## Launching your custom nodes for n8n to Production When you’re ready to go live with custom nodes: - **Push changes to GitHub.** - **Open your project dashboard:** Go to your n8n project in the Diploi console. - **Create a Production deployment:** Click **Create Deployment +** and choose **Production**. - **Pick a cluster size:** Start small; scale when needed. - **Select the source branch:** Typically `main` or `prod`. - **Configure environment variables:** Add any secrets and settings your instance needs (e.g., encryption key, OAuth credentials). - **Create Deployment:** Diploi builds and launches your production instance. Open the deployment URL to complete n8n’s first-run setup and create your admin account and that’s it, your n8n deployment is live! --- ## Configuring a custom domain for your n8n app By default, production runs on a `.diploi.me` subdomain (e.g., `my-automation.diploi.me`). To use your own domain: - **Open the Options tab:** In your Production deployment, go to **Options**. - **Disable auto-generated endpoints:** Toggle off **Use Auto-Generated Endpoints**. - **Add your hostname:** Enable **Use Custom Domain** and enter something like `n8n.yourdomain.com`. - **Save changes**, then update DNS: Create a **CNAME** for your hostname pointing to **edge.diploi.com**. DNS/SSL usually settle quickly, but allow up to \~30 minutes. After that, your n8n instance will be live at your custom domain with HTTPS handled automatically. --- ## New to n8n? Try it in the cloud first for free You can explore n8n on Diploi in seconds without a local setup: - **Option 1 Trial without sign-up**\ Open the **StackBuilder** at , pick **n8n**, and click **Launch**. You’ll get a temporary environment to play with, no account or credit card required. - **Option 2 Quick Launch (if you’re logged in)**\ Create a new project and in **Repository**, choose **Quick Launch**. Diploi provisions a ready-to-use n8n app instantly. These are perfect for testing. For production, create a full project with a GitHub repository so your changes are tracked. --- That’s it! You’ve got n8n running on Diploi, from dev to production, with a custom domain. If you have questions or want to share what you’re building, share with us in Discord or via email at . Happy automating 🤖 --- ## References - Official n8n Documentation - Diploi’s implementation for n8n - Trial launch page for n8n - Diploi Components - Custom Domains ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Creating ready-for-Production Next.js apps using Diploi > Launching Next.js faster than using Vercel and with support for monorepo apps Javier August 22, 2025 Updated October 28, 2025 ###### Getting started with Next.js, without Vercel If you have used Next.js, I’m sure you will be familiar with Vercel. For the most part, Vercel provides a good hosting service, but if you need to use Next.js along with other frameworks on a monorepo, then it is not so good, but Diploi is 😌 In this post, we’ll go over how to create production-ready Next.js apps, with a great deployment experience and support for complex monorepo apps. --- ## Table of contents - [What you need](#what-you-need) - [How to create an app with Next.js](#how-to-create-an-app-with-nextjs) - [Launching your Next.js app to Production](#launching-your-nextjs-app-to-production) - [Configuring a custom domain for your Next.js app in Production](#configuring-a-custom-domain-for-your-nextjs-app-in-production) - [Trying out Next.js for the first time?](#trying-out-nextjs-for-the-first-time) - [References](#references) --- ## What you need - A **GitHub account**, sign up here if you don’t have one yet, - A **Diploi account**, sign up for a free Diploi account at --- ## How to create an app with Next.js 1. In the Dashboard, click **Create Project +** 1. Under **Pick Components**, choose **Next.js** You can add other frameworks from this page if you want to create a monorepo application, eg, Next.js + Bun for backend. 1. In **Pick Add-ons**, select any databases or extra tools you need. 1. Choose **Create Repository** so Diploi generates a new GitHub repo for your project. 1. Click **Launch Stack** This will create a new Project, and by default starts a new Development environment for your Next.js app, once it is ready you will be able to preview your Next.js online, and you can start coding directly in the browser using our built-in IDE, or by connecting remotely via SSH using VS Code, Cursor, or any dev container-friendly IDE. --- ## Launching your Next.js app to Production When your Next.js app is ready, you can start a Production deployment by following these steps: 1. Open your Next.js Project’s dashboard: `https://console.diploi.com//project/` 1. Click **Create Deployment +** 1. Select **Production** as the deployment stage 1. Choose the **cluster size** depending on your needs 1. Pick the **source branch** you want to deploy from, such as `main` 1. Customize any necessary **environment variables** 1. Click **Create Deployment +** Now your Next.js app will be deployed in Production and ready to serve users. --- ## Configuring a custom domain for your Next.js app in Production By default, your app will use a `.diploi.me` URL, for which you can customize its subdomain, but if you want to switch to a fully custom domain: 1. Head to your Production Deployment’s **Options** tab, or go directly to: `https://console.diploi.com//project//deployment//options` 1. In the **Endpoints** section, click to disable **Use Auto‑Generated Endpoints** 1. A field will appear showing your current Diploi subdomain, and a checkbox to enable a custom domain 1. Enable the checkbox and enter your custom domain name 1. Scroll down and click **Save Changes** 1. In your DNS settings, create a **CNAME** record pointing to **edge.diploi.com** The change is usually instant, but sometimes it can take up to 30 minutes for DNS and SSL propagation to complete. --- ## Trying out Next.js for the first time? If you want to try Next.js without having to run a single `npm` command, you can do it using Diploi by either: - **Starting a trial without registering an account** Go to to launch a trial project, or visit the Next.js component page - **Starting a Quick Launch if you have an account on Diploi** Create a new project and in the **Repository** section, select **Quick Launch**. This gives you a temporary environment to explore Next.js without connecting a repo. --- What other frameworks, databases, or services should we support next on Diploi? Let us know on [Discord](https://discord.gg/vvgQxVjC8G)! --- Sign up at [Diploi](https://diploi.com/) and get **50 € in free credits**. --- ## References - - ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Launching a new Node app? How to do it, without configuring a server > Build your next Node.js app with Diploi and have it live right away Javier August 21, 2025 Updated October 28, 2025 ###### Getting started with Node.js on Diploi Node powers so much of the internet these days, and there are hundreds of services that can help you host Node apps, but none might be easier than Diploi. Bold claim, I know. In this guide, I’ll show how easy it is to create a new Node app that is hosted online right from the start without ever touching YAML or annoying server setup wizards. --- ## Table of contents - [What you need](#what-you-need) - [How to create an app with Node](#how-to-create-an-app-with-node) - [Launching your Node.js app to Production](#launching-your-nodejs-app-to-production) - [Configuring a custom domain for your Node.js app in Production](#configuring-a-custom-domain-for-your-nodejs-app-in-production) - [Trying out Node for the first time?](#trying-out-node-for-the-first-time) - [References](#references) --- ## What you need - A **GitHub account**, don’t have one yet? Click here - A **Diploi account**, you can get a free Diploi account here --- ## How to create an app with Node 1. In the Dashboard, click **Create Project +** 1. Under **Pick Components**, choose **Node.js** 1. In **Pick Add-ons**, you can add one or multiple databases to your app 1. Choose **Create Repository**, which will generate a new GitHub repo 1. Lastly, click **Launch Stack** This will create a new Project using Node.js, which will also start a new Development deployment, which will generate a SSL-protected URL for your app. You can start coding in the browser using our cloud IDE, or if you want to use your local IDE, you can connect via SSH using VS Code, Cursor, or any other IDE with support for remote development, so you can start working on your freshly created app without having to run it on your local machine. --- ## Launching your Node.js app to Production When your Node app is ready, you can launch a Production deployment following these steps: 1. Open your Node.js Project’s dashboard: `https://console.diploi.com//project/` 1. Click **Create Deployment +** 1. Select **Production** as the deployment stage 1. Choose the **cluster size** depending on your needs 1. Select the **source branch** you want to deploy from, such as `main` 1. Customize any necessary **environment variables** 1. Click **Create Deployment +** This will create a new deployment for your Node.js app, optimized for Production and ready to serve your users. --- ## Configuring a custom domain for your Node.js app in Production All deployments created on Diploi get an SSL-protected `.diploi.me` URL to direct traffic. If you want to use a custom domain, all you need to do is: 1. Head to the **Options** tab of the Deployment you want to customize, or go directly to: `https://console.diploi.com//project//deployment//options` 1. In the **Endpoints** section, click to disable **Use Auto‑Generated Endpoints** 1. A field will appear showing your current Diploi subdomain, and a checkbox to enable a custom domain 1. Enable the checkbox and enter your custom domain name 1. Scroll down and click **Save Changes** 1. In your DNS settings, create a **CNAME** record pointing to **edge.diploi.com** If you don’t have a custom domain, but want to customize the subdomain automatically generated by Diploi, eg. `foo.diploi.me` to `foobar.diploi.me`, you can do it from the same **Options** tab in your deployment, and after disabling the **Use Auto‑Generated Endpoints** option, an input field will show up showing your current subdomain, all you need to do is rename it to your new subdomain. When you are done, scroll down and click on **Save Changes**. Modifying your domain usually happens instantly, but in some cases, it can take up to 30 minutes for DNS and SSL propagation to be completed. --- ## Trying out Node for the first time? If you haven’t worked with Node.js before and you would like to try it without having to set up folders, repos, or IDEs, you can start a Node project on Diploi in two ways: - 1. **Starting a trial without registering an account** Go to to launch a trial project, or visit the Node component page - 2. **Starting a Quick Launch Project if you have an account on Diploi** Create a new project and in the **Repository** section, select **Quick Launch**. This gives you a temporary environment to explore Node.js without connecting to a repo. --- And that’s all! Now you know how to deploy new Node.js apps in seconds, without ever configuring a server or struggling with SSL certificates. Do you have questions and suggestions for us? Connect with us on [Discord](https://discord.gg/vvgQxVjC8G) and drop us a message. We’ll be happy to talk with you! 😌 --- If you haven’t yet, sign up at [Diploi](https://diploi.com/) and get **50 € in free credits**. --- ## References - - ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Start new apps with Nuejs quickly on Diploi > Learn how to create new Nuejs apps easily and host them online without struggling with server config Javier August 20, 2025 Updated October 28, 2025 ###### Getting started with Nue.js apps, the easy way There are plenty of ways to kick off a Nue.js application, cloning a template from a repo, running `nue create simple-blog`, or rolling your own boilerplate from scratch, but today I’m showing you the absolute easiest approach using Diploi. --- ## Table of contents - [What you need](#what-you-need) - [How to create an app with Nue.js](#how-to-create-an-app-with-nuejs) - [Launching your Nue.js app to Production](#launching-your-nuejs-app-to-production) - [Configuring a custom domain for your Nue.js application in Production](#configuring-a-custom-domain-for-your-nuejs-application-in-production) - [Trying out Nue.js for the first time?](#trying-out-nuejs-for-the-first-time) - [References](#references) --- ## What you need - A GitHub account. If you don’t have one yet, sign up here: --- ## How to create an app with Nue.js 1. **Sign up** for a free Diploi account at 1. In your Dashboard, click **Create Project +**. 1. Under **Pick Components**, choose **Nue.js**. You can also add databases or other frameworks, to your Nue.js stack here. 1. In **Pick Add‑ons**, select any services your app needs (e.g., PostgreSQL, Redis, or MongoDB). 1. Choose **Create Repository** to start from a fresh GitHub repo. 1. Click **Launch Stack**. Diploi will provision a full development environment for your Nue.js app. You’ll be able to: - Preview your app live in the browser. - Edit code directly via the Browser IDE. - Connect over SSH for remote development with VS Code, WebStorm, or any IDE that supports SSH and dev containers. --- ## Launching your Nue.js app to Production When your app is ready for real‑world traffic, follow these simple steps: 1. Navigate to your Nue.js Project’s dashboard at `https://console.diploi.com//project/` 1. Click **Create Deployment +**. 1. Select **Production** as the stage. 1. Pick the **cluster size** that matches your expected load. 1. Choose the **source branch** (e.g., `main`). 1. Configure any **environment variables** your app requires. 1. Hit **Create Deployment +**. Your Nue.js application will be live, and ready to serve users! --- ## Configuring a custom domain for your Nue.js application in Production By default, your production deployment uses a `.diploi.me` domain. To swap in your own: 1. On your Production Deployment’s **Options** tab (or via `https://console.diploi.com//project//deployment//options`), find **Endpoints**. 1. Click **Use Auto‑Generated Endpoints** to disable it. 1. An input field will appear showing your `.diploi.me` URL plus a checkbox for **Custom Domain**. Enable that checkbox and enter your domain. 1. Scroll down and click **Save Changes**. 1. In your DNS provider’s dashboard, create a **CNAME** record pointing your domain to **edge.diploi.com**. It can take up to 30 minutes for DNS propagation and SSL certificate to be ready. --- ## Trying out Nue.js for the first time? Diploi lets you test Nue.js without installing anything locally. Two ways to spin up a sandbox: - **Not yet on Diploi?** Launch a free trial from the Diploi Stack Builder: or go straight to the Nue.js component page: - **Already a Diploi user?** Create a new project, then under **Repository** select **Quick Launch**, you’ll get a throwaway environment preconfigured with Nue.js and any add‑ons you choose, no Git repo required. --- Are there other frameworks or languages you’d like us to support? Let us know on [Discord](https://discord.gg/vvgQxVjC8G)! --- Register at [Diploi](https://diploi.com/) and get **50 € in free credits**. --- ## References - - ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Ship new React apps using Diploi and skip the server config > Create your next React app using Diploi to skip any DevOps work and focus only on the code Javier August 19, 2025 Updated October 28, 2025 ###### Getting started with React on Diploi React is one of the most used and fastest ways to build modern web frontends, and with Diploi, you can host your new React apps faster than with any other hosting service. In this guide, you’ll learn how to launch a fresh React app, using Vite as the default bundler for your app. Using Diploi, your app will be live online in seconds, and best of all, without creating YAML files or doing any server config work. --- ## Table of contents - [What you need](#what-you-need) - [How to create an app with React + Vite](#how-to-create-an-app-with-react--vite) - [Launching your React+Vite app to Production](#launching-your-reactvite-app-to-production) - [Configuring a custom domain for your React + Vite app in Production](#configuring-a-custom-domain-for-your-react--vite-app-in-production) - [Trying out React with Vite for the first time?](#trying-out-react-with-vite-for-the-first-time) - [References](#references) --- ## What you need - A **GitHub account** - No account? Click here > - A **Diploi account** - Need one? Click here > --- ## How to create an app with React + Vite 1. In the Dashboard, click **Create Project +** 1. Under **Pick Components**, choose **React + Vite**. Here you can also add a backend framework to create a monorepo app, eg, React+Vite for frontend and Hono for backend 1. In **Pick Add-ons**, you can add one or multiple databases to your app 1. Choose **Create Repository** to generate a new GitHub repo 1. Finally, click **Launch Stack** You’ve now got a new React+Vite project running on Diploi. By default, every new project starts with a fresh Development deployment. Under the hood, Diploi uses Kubernetes to spin up the infrastructure for your deployment. Think of it like having a virtual machine dedicated to running your React + Vite app and serving it online over an SSL-protected URL. You can start coding right away without touching your local machine by using Diploi’s browser IDE, or connecting your local code editor directly to the remote development environment, without `git clone` or `npm install` to get started coding. --- ## Launching your React+Vite app to Production When you are ready to launch your app to Production, follow these steps to start a Production deployment: 1. Open your React-Vite Project’s dashboard: `https://console.diploi.com//project/` 1. Click **Create Deployment +** 1. Select **Production** as the deployment stage 1. Choose the **cluster size** depending on your needs 1. Select the **source branch** you want to deploy from, such as `main` 1. Customize any necessary **environment variables** 1. Click **Create Deployment +** That’s all it takes to get your app on Production. Let’s now talk about how you can customize your deployment’s domain. --- ## Configuring a custom domain for your React + Vite app in Production When you launch a new deployment, Diploi automatically creates an SSL-protected URL that ends in `.diploi.me`. To instead use a custom domain, you need to do the following: 1. Go to the **Options** tab, which you can find by navigating to the dashboard of the Deployment. The URL will look something like: ```plaintext https://console.diploi.com//project//deployment//options ``` 2. Scroll to the **Endpoints** section and turn off **Use Auto-Generated Endpoints** 2. You’ll now see a field showing your current deployment subdomain. Check **Use custom domain**, then type in the domain name you want to use 2. Scroll to the bottom and click **Save Changes** 2. In your domain provider’s DNS settings, create a **CNAME** record that points your domain to: ```plaintext edge.diploi.com ``` ✅ **Done!** This update will take effect instantly, but allow up to 30 minutes for DNS and SSL propagation. --- ## Trying out React with Vite for the first time? If this is your first time trying React + Vite, you might not want to bother with all the usual setup and configuration. With Diploi, you can skip the boring parts and jump straight into coding, so no local install is required. You’ve got two easy options using Diploi: **Option 1 - Start a trial without an account** Head to to launch a trial project instantly. You can also go directly to the React + Vite component page: **Option 2 - Quick Launch with a Diploi account** If you already have an account, create a new project and in the **Repository** section choose **Quick Launch**. This gives you a temporary environment to experiment with React + Vite without connecting a repo. --- Now you know the easiest way to take a new React + Vite app from first commit to production, and the best part is that **no DevOps required**. If you want to get involved with Diploi, join our [Discord](https://discord.gg/vvgQxVjC8G). We’d love to hear from you! 🙂 --- Sign up for [Diploi](https://console.diploi.com/) for free and get €50 in credits to launch your React + Vite projects. --- ## References - - - ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Supabase on Diploi > How to get started with Supabase, using Diploi to host a project. Javier September 25, 2025 Updated October 28, 2025 ###### Deploy Supabase in minutes with Diploi, with PostgreSQL preconfigured, and DevOps not required. Supabase is an open-source alternative to Firebase, which offers an instant Postgres database, authentication, storage, and more. With Diploi, you can get Supabase up and running in a fully-managed cloud environment, with no local setup or manual server configuration. In this post, we’ll walk through getting started with Supabase on Diploi, deploying it to production, and adding a custom domain. --- ## Table of contents - [Getting started with Supabase on Diploi](#getting-started-with-supabase-on-diploi) - [Launching your Supabase project to Production](#launching-your-supabase-project-to-production) - [Configuring a custom domain for your Supabase project](#configuring-a-custom-domain-for-your-supabase-project) - [Trying out Supabase for the first time?](#trying-out-supabase-for-the-first-time) - [References](#references) --- ## Getting started with Supabase on Diploi ### What you need - A GitHub account - A Diploi account Signing up in Diploi is free, and does not require credit card. ### How to create a Supabase project After signing in: 1. Click **Create Project +** in your Dashboard 1. Under **Pick Components**, select **Supabase** 1. Optionally attach any **Add-ons** (like Redis, etc.). PostgreSQL is already included by default 1. Under **Repository**, choose **Create Repository** so Diploi scaffolds a GitHub repo for you 1. Click **Launch Stack** to start your environment This will: - Scaffold your app with a GitHub repo - Start a Remote Development environment where you can create custom Supabase Functions - Launch a live preview URL where you can test Supabase right away - Allow you to manage ENV variables from the `options` tab To access the Remote Development environment, you can: - Use the browser IDE: - Or connect via SSH using your local editor: When you access the live version of Supabase, you’ll be able to manage your Supabase instance. --- ## Launching your Supabase project to Production If you are developing a full-stack app or creating custom Supabase Functions, once you are ready to start using your application in production, all you need to do is this: 1. Push changes to GitHub 1. Open your project dashboard in Diploi 1. Click **Create Deployment +** and select **Production** as the stage 1. Choose a **cluster size** 1. Select the **Git branch** that you’ll use for production (e.g. `main`) 1. Configure any **environment variables** your Supabase app needs 1. Click **Create Deployment** Diploi builds your production instance and gives you a live URL under the `*.diploi.me` domain. Next, let’s assign a custom domain for your Supabase deployment. --- ## Configuring a custom domain for your Supabase project To make your Supabase deployment available under your own domain: 1. Go to your Production deployment’s **Options** tab 1. Toggle off **Use Auto-Generated Endpoints** 1. Enable **Use Custom Domain** and input your domain (e.g. `db.mydomain.com`) 1. Save changes 1. In your domain DNS settings, create a **CNAME** pointing your hostname to `edge.diploi.com` Diploi handles the SSL certificates automatically. This change usually happens instantly, but sometimes the DNS updates can take up 30 minutes to propagate. --- ## Trying out Supabase for the first time? No need to commit to anything. You can test Supabase instantly on Diploi: - **Trial without signing up** Visit , select Supabase, and click Launch - **Quick Launch with your Diploi account** Create a new project, and in **Repository**, choose **Quick Launch** --- ## References - Supabase Docs - Diploi Supabase Component - Launch Supabase on Diploi - Diploi Components - Custom Domain Guide: ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Launching SvelteKit apps, from Development to Production using Diploi > With the convenience of Vercel and the flexibility of Replit, all in a single platform, to create SvelteKit-powered apps super fast Javier August 18, 2025 Updated October 28, 2025 ###### Getting started with SvelteKit apps, the easy way There are many ways to launch apps with SvelteKit, like classic `npm init -y` or taking one of the thousands of boilerplate templates hosted on GitHub, but today I’m talking about the absolute easiest one. If you don’t want to read, check this short video tutorial. --- ## Table of contents - [What you need](#what-you-need) - [How to create an app with SvelteKit](#how-to-create-an-app-with-sveltekit) - [Launching your SvelteKit app to Production](#launching-your-sveltekit-app-to-production) - [Configuring a custom domain for your SvelteKit application in Production](#configuring-a-custom-domain-for-your-sveltekit-application-in-production) - [Trying out SvelteKit for the first time?](#trying-out-sveltekit-for-the-first-time) - [References](#references) --- ## What you need - A GitHub account, if you don’t have one, you can create it here ## How to create an app with SvelteKit - Create an account on Diploi, it’s free - Once you are in the Dashboard, click on “Create Project +” - Now you need to select the stack for your app. In the “Pick Components” section, select **SvelteKit**. You can add other frameworks to work along with your SvelteKit app. This also applies to the “Pick Add-ons” section, where you can choose the database for your app. - Next, you need to choose “Create Repository” so your new app will start with a fresh repository. - Finally, click “Launch Stack”. That’s it, Diploi will then start a Development environment for your new SvelteKit-powered app where you can preview your app live online and you can code directly on the browser using the Browser IDE or connect to the remote development environment using SSH, with VS Code, Cursor, Windsurf and any other IDE that supports remote SSH connections and dev containers. --- ## Launching your SvelteKit app to Production After your app is ready to be launched on Production, all you need to do is: - Go to your SvelteKit Project’s dashboard, where you can manage the existing Deployments of your app, eg. `https://console.diploi.com//project/` - From your Project’s dashboard, click on “Create Deployment +” - Next, you need to choose the “Production” stage for your new Deployment. - Then choose the size of the cluster for your Deployment. - Select then the source branch that your Deployment will use, eg. “main” - Now you can customize the environment variables that your Production deployment will use - Lastly, click “Create Deployment +” And now your SvelteKit app is ready to receive users! --- ## Configuring a custom domain for your SvelteKit application in Production At this point, your application will be using a `.diploi.me` domain by default, which you can change instead to use a custom domain. To configure use a custom domain for your Production Deployment, you need to: - Go to your Production Deployment’s options tab, visible from the dashboard or by going directly to its URL, eg. `https://console.diploi.com//project//deployment//options` - Find the section “Endpoints”, where you will see the option “Use Auto-Generated Endpoints” enabled by default. Click on it to disable it. - An input field with your current `.diploi.me` URL will appear with a checkbox below to enable a custom domain. When you click on it, you’ll be able to change your domain. - When you are done, scroll down the page and click “Save Changes” - Next, you need to go to your domain’s DNS settings and create a new CNAME record that points to **edge.diploi.com** It can take up to 30 minutes for your new domain and SSL certificate to be fully set up and working correctly. --- ## Trying out SvelteKit for the first time? On Diploi, you have the option to test-drive tools without having to install anything on your machine. For SvelteKit, you can create a fresh development environment on the cloud using Diploi, in two ways: - **If you are not registered on Diploi**, you can launch a free trial, either from here , where you can add test SvelteKit with other frameworks or from the SvelteKit component page, if you want to run a testing environment only using SvelteKit with a database. - **If you are registered on Diploi**, you can create a new project and in the **Repository** section, select “Quick Launch”, that way, you will be starting an environment without a repository, intended to be used to try out the stack you selected. --- Are there other frameworks or languages you would like us to add? Feel free to share it with us on [Discord](https://discord.gg/vvgQxVjC8G). --- Register in [Diploi](https://diploi.com/) and get 50€ in free credits. --- ## References - - ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # How to create dynamic GitHub Actions based on the contents of a repository > If you are here, you probably know what GitHub Actions are and understand the basics of... Javier April 2, 2025 [Read on Dev.to](https://dev.to/diploi/how-to-create-dynamic-github-actions-based-on-the-contents-of-a-repository-50j8) --- ###### If you are here, you probably know what GitHub Actions are and understand the basics of YAML --- ## Dynamic GitHub Actions GitHub Actions allow you to create jobs programmatically by using something called [`matrix` strategy](https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs#matrix-context). In this guide, we'll show how we use `matrix` strategies at Diploi to generate dynamic GitHub Action jobs, based on the configuration that applications generated using Diploi have For context, all applications generated on Diploi, have a mono-repo folder structure and every time a user launches a deployment, Diploi uses Kubernetes to create isolated Docker containers for each component (eg. Nextjs, Node, Svelte, etc) that the application created has. Every time a user pushes a new update to GitHub, we need to update the Docker images that Kubernetes will be running For an application on Diploi, we build two Docker images per component in the stack, one image for development, which has a cloud development environment and another image for staging/production environments without a development environment. The components of an application built using Diploi come from our [Stack Builder](https://dev.to/diploi/easily-create-complex-stacks-in-just-a-few-clicks-new-release-3gdl), where you can configure a new application --- ## Walkthrough For this guide, we'll use an application with [Bun](https://diploi.com/component/bun) and [React+Vite](https://diploi.com/component/react-vite) In the backend, each component that's part of the stack of this application is sent to an API that generates the application's folders and creates a `diploi.yaml` file which serves as the blueprint for our implementation of Kubernetes and Docker, plus `Build.yaml` file for our GitHub Action The output from the API is a new application with a folder structure that looks like this: ``` root/ .github/ workflow/ Build.yaml bun/ vite/ diploi.yaml ``` We'll focus on the `Build.yaml` file, which it has all the instructions that will be run by the GitHub Action runner and it's the same file we generate for all applications created using Diploi's Stack Builder. Let's look at `Build.yaml` closer: ``` name: Build Components on: push: branches: - '*' jobs: define-components: name: Define Components runs-on: ubuntu-latest outputs: components: ${{ steps.diploi-meta.outputs.components }} steps: - name: Checkout code uses: actions/checkout@v3 - id: diploi-meta name: Diploi meta uses: diploi/action-components@v1.6-alpha run-builds: name: Build ${{ matrix.name }} ${{ matrix.stage }} runs-on: ubuntu-latest needs: define-components strategy: fail-fast: false matrix: include: ${{ fromJSON(needs.define-components.outputs.components) }} steps: - name: Checkout code uses: actions/checkout@v3 - name: Diploi build uses: diploi/action-build@v1.7-alpha with: ${{ matrix }} env: project: ${{ secrets.DIPLOI_REGISTRY_PROJECT }} registry: ${{ secrets.DIPLOI_REGISTRY_HOSTNAME }} username: ${{ secrets.DIPLOI_REGISTRY_USERNAME }} password: ${{ secrets.DIPLOI_REGISTRY_PASSWORD }} ``` --- ### Deep dive In a nutshell, our GitHub Action is divided in two jobs, `define-components` and `run-builds`, where `define-components` will generate the components based on our choices from the Stack Builder, which then will be passed to `run-builds` to create the builds for each component **Let's breakdown these two jobs in detail:** `define-components` - This job is in charge of creating an array of objects with the metadata from each component and add-on that will be part of our application. The action is stored on a separate repository, which houses an `action.yml` file which is the entry point for the GitHub Action runner and a node script with the code that takes in the components and add-ons details by reading the `diploi.yaml` file in the root of our monorepo. ``` name: 'Diploi Component Metadata Action' description: 'An action that collects component metadata from a Diploi stack' branding: icon: 'package' color: 'purple' outputs: components: description: 'List of components (identifier, name, folder, type, ref) that need to be built' runs: using: 'node20' main: 'index.js' ``` The `define-components` job executes a file called `index.js` that when the job is completed, will generate an output array which then will be used by the next job `run-builds`, ``` //... const componentOutput = { identifier: component.identifier, name: component.name || component.identifier, folder: component.identifier, type: isDevImageAvailable ? 'main' : 'main-dev', }; //... core.setOutput('components', JSON.stringify(componentsOutput)); ``` Let's take a look at the output of the job ``` [{"identifier":"bun","name":"Bun","folder":"bun","type":"main"}, {"identifier":"bun","name":"Bun Dev","folder":"bun","type":"dev"}, {"identifier":"react-vite","name":"React + Vite","folder":"react-vite","type":"main"}, {"identifier":"react-vite","name":"React + Vite Dev","folder":"react-vite","type":"dev"}] ``` This output will be used as arguments that will dynamically generate the next job steps --- `run-builds` - Until this point, I talked about the `run-builds` job in singular, but as you might have noticed, the output from `define-components` will be an array which will then be used to generate an instance of the `run-builds` job for each object in the array In `run-builds` we use the `matrix` strategy to make the job into dynamically generated jobs. This makes our process scalable since we don't need to have a unique action per component, and instead we can have a single action that takes each output object properties and runs a separate job dynamically Now that you have seen `matrix` strategies in action, you might have an idea as to how to generate jobs programmatically when running GitHub Actions --- Go out there and make us proud! 🫡 --- ###### Prefer to not worry about GitHub actions when launching your next application? [Try Diploi ✨](https://diploi.com/) --- **References:** ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # How We Solved Infrastructure as Code > Infrastructure as Code (or IaC for short) has been gaining traction recently—and for good reason. It... Tuomas December 3, 2024 [Read on Dev.to](https://dev.to/diploi/how-we-solved-infrastructure-as-code-2ldn) Infrastructure as Code (or IaC for short) has been gaining traction recently—and for good reason. It brings with it a ton of benefits, but can often be challenging to get started with. Many cloud services still lack support for it, forcing users to navigate a maze of control panels to make changes to their infra. At [Diploi](https://diploi.com/), we looked at existing solutions such as Terraform, Pulumi, AWS CloudFormation, and Azure ARM Templates but found that none fully aligned with our motto of providing a "magical development experience". While these tools are highly versatile and capable of handling almost any infrastructure configuration, they are often difficult to master and excessively verbose. Setting up a single service often requires creating multiple templates and configuration files. As that was not the developer experience we were looking for, we decided to build our own easy-to-use IaC solution. --- ## What is Infrastructure as Code? For developers, Infrastructure as Code (IaC) essentially means replacing cloud provider management dashboards with config files. These files contain everything necessary to replicate a specific environment, ensuring that the environment your code runs on is always set up correctly and consistently. Typically, your IaC definitions would specify the following: - **Deployment Target**: Where your code will be deployed, such as AWS or Azure. - **Required Services**: The services needed to support your application. - **Virtual Machine Setup**: Configuring any necessary VMs and installing dependencies. - **Network Configuration**: Setting up & securing the network. Provisioning domain names. Configuring DNS. - **Application Execution**: Deploying and running the application code. --- ## Our Implementation We thought a lot about the best way to implement IaC into [Diploi](https://diploi.com/). Our solution had to be intuitive, developer-centric, and highly customizable.\ We settled on a **component-based model** that allows users to easily configure their stack without making the config overly verbose. The more detailed config for a component, such as HELM charts and other setup files, are housed in dedicated GitHub repositories maintained by the component owners.\ However, users can also specify local path for a component, enabling custom components to be seamlessly inlined within the projects repository.\ This approach gives our users the best of both worlds: a simple, easy-to-use config combined with limitless customization options, including custom Docker files, HELM charts, and more.   These simple config files, combined with our intuitive [Stack Builder](https://dev.to/diploi/diploi-stack-builder-32n4), create a developer experience within [Diploi](https://diploi.com/) that is magical ✨ and unparalleled. --- ## Benefits of Our Implementation Our implementation in [Diploi](https://diploi.com/) comes with a long list of benefits, many of which are true for any IaC system. Here are some of the more interesting ones in a easily digestible list: 1. Versioning with Git 🌳 - Maintain separate infra in different branches - Diffs & blames for infra changes 1. Self-Documenting Config Files 📝 - View all infra components in a single file - Clickable links to find information on each component 1. Inlining Components 🏠 - Include component config files directly in the local repository - Permanent version pinning and customizations We’re still working on our system, so stay tuned for a more detailed explanation [in the future](https://dev.to/diploi/diploi-roadmap-for-2024-1nde). 😉 --- By the way, we’re currently looking for developers to join our internal testing program. If you’re interested in trying out our version of IaC before its official release, leave a comment, and I’ll get in touch! ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Using Cursor with apps built with Lovable, and hosting without Lovable Cloud > Import and deploy Lovable AI apps directly from your GitHub account or public repositories and code with Cursor Javier October 17, 2025 Updated October 28, 2025 --- ## Table of contents - [How to expand Lovable apps with Cursor and flexible hosting](#how-to-expand-lovable-apps-with-cursor-and-flexible-hosting) - [What is possible with Diploi](#what-is-possible-with-diploi) - [Importing a Lovable app to Diploi](#importing-a-lovable-app-to-diploi) - [Getting started with a Development environment](#getting-started-with-a-development-environment) - [How to connect Cursor to your Lovable app](#how-to-connect-cursor-to-your-lovable-app) - [Creating a Production deployment for your Lovable app](#creating-a-production-deployment-for-your-lovable-app) - [Adding a custom domain to your deployed Lovable app](#adding-a-custom-domain-to-your-deployed-lovable-app) - [Expanding your Lovable app with Components and Add-ons](#expanding-your-lovable-app-with-components-and-add-ons) - [Bringing It All Together](#bringing-it-all-together) - [References](#references) --- ## How to expand Lovable apps with Cursor and flexible hosting When you create a new application with Lovable, you get a lot done for you with just one prompt, which is great to get your project going, but! If you are here, it is because you also noticed that this is not enough. Maybe you reached the limits of what’s possible with Lovable, got tired of context pollution, or limited branching support when deploying your app. Lovable’s context can get polluted, and after a few chats, you end up either spending credits to fix bugs that the AI has introduced as it goes or looking for ways to restore your app to a point when it was working. Other times, you might want to use tools like Cursor, so you can target specific areas of your codebase and work along with Cursor’s AI to improve your product, but since Lovable has it’s own cloud and environment settings, you might cause unnintended issues, when your app is not able to run on Lovable and you need to find an alternative to host it. Because of these issues, we decided to create something to help people who use Lovable extensively by adding a way to import apps built with Lovable on Diploi. As a developer platform, with Diploi, we give you a way to host and code without the usual work of running apps locally or setting up servers. ## What is possible with Diploi Not only can you import your apps or start from zero, but you can also expand what’s possible for your apps by using Diploi, where you can: - add a backend for your imported apps, - migrate from paid Supabase to open-source Supabase, - add additional databases, - add blogging with Ghost, - and add automated tasks with n8n, The best part is that you can host all of these services along your Lovable app, within the same server cluster, so you only pay for one service, rather than paying for multiple servers to host each part of your full-stack application. You get a smooth hosting experience, where you can add custom domains, and the option to deploy preview or production environments for your app without having to set up CI/CD pipelines or SSL certificates. You can add components and add-ons in Diploi just by modifying a [diploi.yaml](https://docs.diploi.com/reference/diploi-yaml) file, which is created when you import an app from Lovable. So let’s go over a walkthrough. In this blog, we’ll show you how to import an application created using Lovable. Let’s get going 👨‍🏭 --- ## Importing a Lovable app to Diploi In this walkthrough, we’ll be importing an application stored on GitHub and built with Lovable. The app has a soundboard interface where you can play sounds and it allows you to add new sounds to the list available. If you want to use this same application for testing, here’s the public repository which you can use to import the app to your own Diploi account: You can see the live app here: [https://demo—soundboarded.diploi.me/](https://demo--soundboarded.diploi.me/) Let’s get started by creating a new project and starting a Development environment, where you can start coding with Cursor right away. --- ### Getting started with a Development environment We’ll assume that you already have a GitHub account and at least one project built with Lovable (you can use the repository we used for this guide too). #### 1. Create a Diploi Account Now you’ll need to create an account in Diploi, which is free. You can do it from [console.diploi.com](https://console.diploi.com). #### 2. Create a new project Once you finish creating an account, you will be welcomed with the Stack Builder, which is the place to create a new application from zero or import a repository from GitHub. #### 3. Select the repository you want to import From the Stack Builder, choose the option **Import Repository** and you have the option to: - Select the application you want to import from your list of repositories. - Importing from a URL, which allows you to use the URL from any repository you own or public repositories, even if you are not the owner. #### 4. Analyze the repository To make sure that the repository will be able to run on Diploi, you must click **“Analyze repository”** so Diploi can check the configuration of your project and prepare your deployment environment. If the analysis is successful, you will get a notification indicating that your repository contains a Lovable application. #### 5. Launching the application Something we must note is that depending on the ownership of the repository, the steps after the repository has been analyzed are different. ##### If you are the owner of the imported repository You can just launch your application instantly, without having to configure additional settings for your deployment. Any updates you made to the code will be linked to the repository you imported. ##### If you are importing a repository from someone else You can customize the stack for your imported Lovable app, so you can add other services like [Bun](https://diploi.com/component/bun) to create a backend for your app or [Ghost](https://diploi.com/component/ghost) to add a blog. Diploi allows you to create a new repository for your application, since you don’t own the imported repository. --- At this stage your app should be ready to be launched, so all you need to do is click **“Launch Stack”** and a new Development environment will be created for you. --- ### How to connect Cursor to your Lovable app Now your application should be running, and you should see something like this: From here you can preview the application live, by clicking on **“View App”**. And you can also access the Remote Development environment where you can start coding your application, that allows you to start coding without installing anything. Now, we want to connect Cursor, so we need first to add an SSH key to connect your computer to the Remote Development environment. Here’s what you need to do. #### 1. Create an SSH key There are multiple ways to generate an SSH key, but in my opinion the easiest way to do it is by using the command `ssh-keygen` from whatever Terminal application you have available in your computer. The steps you must follow are: 1. Open a Terminal - in **Linux**, you can open the terminal by pressing `Ctrl`+`Alt`+`T` - in **Mac**, open the Spotlight Search by pressing `Command`+`Space` and then typing “terminal”. - in **Windows**, you can open the terminal by opening Git Bash from your apps (If you don’t have it, you can download it here ) 1. Then type the command `ssh-keygen`, which will generate an SSH key, which by default will have the name `id_ed25519`, but you can assign a different name and store it on a different folder. For convenience, use the default filename and location, since Cursor by default will use the same filename and location to fetch your SSH keys. 1. After the filename has been assigned, you will have the option to assign a passphrase to use your SSH key. You can leave it empty by just pressing enter. #### 2. Add the SSH Public Key in Diploi By now, `ssh-keygen` would have generated 2 files. If you used the default name, the filenames would be `id_ed25519`, which stores your Private Key and “id\_ed25519.pub\`, which stores your Public Key. The next steps are to copy your Public Key, which you can do by reading and copying the contents from `id_ed25519.pub`, and pasting them in your Diploi account settings. 1. To copy the contents of your Public Keyu file, you can use any text editor to open and copy the contents of the file, or from the terminal, you can use the command **cat**, so if you used the default name and location, the command would look like this: `cat ~/.ssh/id_ed25519.pub`, and after pressing enter you should see in the terminal something like this: From there, you can just select the text starting from “ssh-ed25519…” and then press `Ctrl`+`Shift`+`C` 1. Now you need to add the copied text in Diploi, which you can do from the settings page at `https://console.diploi.com//settings`, scroll down to the **“authentication”** section, and then click on **“Add New SSH Key”**. 1. And the last step is to paste the contents we copied before inside the **“Public Key”** text field, and then press **“Add SSH Key”**. Now we are ready to open the imported Lovable app with Cursor. #### 3. Opening your app with Cursor Now we are ready to open the imported app from Lovable using Cursor. 1. Go to the deployment page and enable Cursor, from the **“Develop”** section, press the button **+** and you’ll be able to see the **“Open in Cursor”** option. 1. To pin the **“Open in Cursor”** button to your deployment, just click on the pin icon next to the text. 1. When you click on the button to open Cursor, the app will use SSH to connect to the development environment. --- And that’s it! Now you can connect Cursor to any other app you import or create in Diploi. --- ## Creating a Production deployment for your Lovable app Once you get your application to a stage where it is ready to be launched in Production, you can create a new deployment that will be used for that specific case. Before getting started, you must first push your updates to GitHub, so your application has your changes plus the files that Diploi added to your repository in order to be able to run your application. If you don’t push files that Diploi creates for your repository, then your Production deployment will fail to start. #### 1. Create a new deployment Go to the project page, and click on the button **“Create Deployment”**. #### 2. Select the stage for the new deployment On the deployment creation page, select the stage for the deployment as **“Production”**. You can also choose “Staging” if you want to generate a deployment intended for testing. #### 3. Choose the size for the cluster You can choose between 4 cluster specs, and in general we recommend you start with **S** size clusters when launching Lovable apps to Production, since you can always resize the cluster later if your application starts getting a lot of traffic. #### 4. Select the branch you will deploy to Production If you have your production version for your app on a different branch than main, here you can select it for your new Production deployment. #### 5. Configure the environment variables for Production If your Lovable app uses environment variables, in this section you can add them. --- And that should be all you need to set up your new **“Production”** deployment, just click **Create Deployment** and you’ll have a Production environment live. --- ## Adding a custom domain to your deployed Lovable app Now that your app is in Production, you probably want to use a custom domain too. Let’s walk through over the steps you need to follow. #### 1. Open the Options tab from the Production deployment dashboard #### 2. Turn off auto-generated endpoints #### 3. Enable “Use Custom Domain” and enter your hostname #### 4. Create a CNAME record from your domain’s DNS settings, pointing to `edge.diploi.com` --- It is common for the custom domain to be fully set up within 1 to 2 minutes, but it can take up to 30 minutes for the update to propagate and for your website to be reachable and SSL-protected. --- ## Expanding your Lovable app with Components and Add-ons If you want to elevate your application with a proper Backend, blogging, or databases, you can add components like **FastAPI**, **Ghost**, **n8n**, etc., and add-ons like **Redis** and **Supabase**. #### 1. Open the diploi.yaml file To add them, all you need to do is access your app’s folder and find the `diploi.yaml` file. When you open it, the content for your Lovable app would look like this: ```yaml diploiVersion: v1.0 components: - name: Lovable identifier: lovable folder: / package: https://github.com/diploi/component-lovable#v1 addons: [] ``` The `diploi.yaml` tells Diploi how to build your app’s environment. Each component and addon defined for your app has a name, identifier, and a package URL pointing to the Diploi component repository. #### 2. Add new components and addons to your Lovable add To add a new component for your app’s stack, all you need to do is add a new entry to the components or addons list with all of the properties required to define them. For example, let’s say we want to add **FastAPI**, **Postgres**, and **Redis**, your `diploi.yaml` would then look like this: ```yaml diploiVersion: v1.0 components: - name: Lovable identifier: lovable folder: / package: https://github.com/diploi/component-lovable#v1 - name: FastAPI identifier: fastapi package: https://github.com/diploi/component-fastapi#main addons: - name: Redis identifier: redis package: https://github.com/diploi/addon-redis#main - name: Postgres identifier: postgres package: https://github.com/diploi/addon-postgres#main ``` After modifying the `diploi.yaml` file, if you go back to your deployment’s dashboard, you’ll see a notice listing the pending changes for your environment. By clicking **“Apply Changes”**, Diploi will proceed to start additional containers to host the new component and addons as pods in the same cluster that already hosts your Lovable app. --- ## Bringing It All Together In summary, importing a Lovable app into Diploi would allow you to elevate what your apps can do and how you can host them, without having to do manual work setting up servers or configuring anything manually. For more details about the `diploi.yaml` syntax and available components/add-ons, check the Diploi docs. By importing your Lovable app into Diploi, you effectively upgrade it from a frontend prototype into a full-stack, production-ready app, without leaving the Diploi console. You get one-click deployments, remote dev environments, and pay-as-you-go hosting all in one place. And the best part is that you can still continue using the Lovable AI chat for your frontend, because the changes that Diploi makes on your repository’s folder structure and the files added do not conflict with Lovable’s system. --- If you are building something using Lovable and Diploi, please let us know! You can connect with us directly on Discord or via email. We’ll be happy to talk with you and help however we can. Until the next one! 😎 --- ## References - Diploi Components - Diploi Addons - Custom Domains - Adding an SSH key in Diploi ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Importing Lovable apps and more from an existing Repository to Diploi > You can now import apps directly from your GitHub account or public repositories, and host them instantly on Diploi Javier September 26, 2025 Updated October 28, 2025 ## Table of contents - [Import Lovable apps from GitHub Repositories](#import-lovable-apps-from-github-repositories) - [Getting started with a Development environment](#getting-started-with-a-development-environment) - [Creating a new project](#creating-a-new-project) - [Start a New Project with Import Repository](#start-a-new-project-with-import-repository) - [Adding Components and Add-ons (for public repositories)](#adding-components-and-add-ons-for-public-repositories) - [Starting the imported project](#starting-the-imported-project) - [Starting your first deployment](#starting-your-first-deployment) - [Creating a Production Deployment](#creating-a-production-deployment) - [Using a custom domain with imported applications](#using-a-custom-domain-with-imported-applications) - [Supported frameworks](#supported-frameworks) - [References](#references) ## Import Lovable apps from GitHub Repositories We are releasing today the capability to **import apps built using Lovable**, all you need is to import from your GitHub account or if it is a public project in GitHub, you can import it via URL. But that’s not all! We are also releasing in beta, the option to **import any Repository**, although it’s not stable yet, you can try it out. We are looking for early adopters to get feedback and improve how imported projects are launched using Diploi and ensure reliability. If you test these features, please share with us how your experience goes. You can do it via [Discord](https://discord.gg/vvgQxVjC8G) or email us at . --- ### Getting started with a Development environment To start importing a Repository, you first need to have: - A GitHub account, required to register in Diploi. - A Diploi account. You can sign up for free at [console.diploi.com](https://console.diploi.com) #### Creating a new project Once you are logged in, if it’s your first time in Diploi, you’ll be welcomed with the project creation wizard. If it’s not your first time in Diploi, you can get started by creating a new project. #### Start a New Project with Import Repository By creating a new project, you’ll be welcomed by the Stack Builder, where you must select the tab **Import Repository**. There you’ll have two options: 1. Pick a Repository Where you can choose a Repository you own, either public or private. 1. or Import from URL Which allows you to import any public Repository. After you choose an option, all you need to do is click **Analyze Repository**, so our system can review the contents of the Repository to determine the best way to run it. If you are using a Repository that you own, Diploi will use that same Repository as the base, so you won’t be able to add components or add-ons from the Stack Builder in the project creation wizard. But in case you import a project from a public URL that you don’t own, you’ll be allowed to add additional components and add-ons to the application you are trying to deploy, and Diploi will create a new Repository with the contents of the public Repository you added. **IMPORTANT** > As I mentioned in the beginning, the Import Repository feature has been tested mainly with projects built with Lovable. Of course, we designed it to work with ALL of our supported frameworks and languages, but it is not stable yet, so if you try import other apps, it might wrongly detect how to run it. > > If you find issues trying to run an app built with a framework or language supported on Diploi, please let us know! [Discord](https://discord.gg/vvgQxVjC8G) | . #### Adding Components and Add-ons (for public repositories) As I mentioned just before, if you import a public Repository that you don’t own, you’ll be able to add components and add-ons. For example, a common choice for projects built with Lovable would be to add Supabase. If you instead choose to import a Repository you own, you won’t be able to add custom components or add-ons. #### Starting the imported project Now that the stack for our application is ready, we can create a Repository to store the new application. If instead you are using your own Repository, you won’t be prompted to create a new repo. For the rest of this walkthrough, we’ll use a public Repository that we don’t own (You can try it yourself by using this URL: `https://github.com/wickathou/gift-sparkle-maker`), to import an application built with Lovable, and we’ll add Supabase, Ghost, n8n, FastAPI, and Redis. You might notice that Postgres and MariaDB were added too, which come bundled by default as they are required by n8n and Ghost, respectively. **Note** > For projects created using Diploi, the process is more straightforward, since the system can use the `diploi.yaml` file directly, so the import will be guaranteed to work. Once you are ready, just click **Launch Stack** to start a Development environment. #### Starting your first deployment After the import is completed and you launch, Diploi will: - Set up a **Remote Development** environment - Scaffold your project structure and Repository - Install dependencies and build your app You can get straight to coding your app by using the Remote Development environment in two ways: - Opening the **browser IDE**, or - Connecting via **SSH** with your local editor (VS Code, Cursor, etc.) Or if you prefer, you can also use `git clone ...` to run your application locally. Diploi generates a Dockerfile for all parts of your application, which you can use to create local images and run your application as containers. **IMPORTANT** > Due to safety reasons, Diploi will not push the changes it does to your application, so before you deploy to production, make sure to **push any changes** Diploi made during the setup for your Repository. --- ### Creating a Production Deployment Once you push the changes to your project made by Diploi, you can create a new deployment for Staging or, more importantly, Production! To do just that, all you need to do is this: 1. Push your development changes to GitHub 1. Open your project dashboard in Diploi. 1. Click **Create Deployment +** and select **Production** as the stage. 1. Choose a **cluster size**. 1. Select the **Git branch** that you’ll use for production. 1. Configure any **environment variables** your imported app needs. 1. Click **Create Deployment**. Diploi provisions your production instance and gives you a live URL on \*.diploi.me. Now let’s point a custom domain to your imported project. --- ## Using a custom domain with imported applications By default, your production URL is a `.diploi.me` subdomain (for example, `my-imported-app.diploi.me`). To use your own domain: 1. Open the **Options** for the deployment you can point to, for example, your Production deployment. 1. Turn off the **auto-generated endpoints**. 1. Enable **Use Custom Domain** and enter your hostname, for example, `yourdomain.com`. 1. Then update your domain’s DNS, by creating a **CNAME** record pointing to `edge.diploi.com`. DNS and SSL usually finalize quickly, but it can take up to 30 minutes to be ready. After that, your imported application will be live with your custom domain with SSL protection configured automatically. --- ## Supported frameworks The GitHub import feature has been tested mainly with apps that use Node.js, but mostly apps built with **Lovable**. To give more clarity, divided the level of support that each framework/tooling has when importing an application to Diploi. - Fully supported: Apps built with these frameworks/tooling will be able to run in Diploi with minimal changes. - Beta stage: Imported apps might be able to run, but they are not stable or require changes. - Experimental: Apps might require major changes to their configuration in order to run. We created this table to explain how well supported each framework is. Framework / Tooling | Support Level | Recommended for Production Diploi | Fully supported | ✅ Lovable | Fully supported | ✅ React-Vite | Fully supported | ✅ Node.js | Fully supported | ✅ Astro | Beta stage | ❌ Deno | Beta stage | ❌ Bun | Beta stage | ❌ Hono | Beta stage | ❌ Next.js | Beta stage | ❌ Nue | Beta stage | ❌ FastAPI | Experimental | ❌ Flask | Experimental | ❌ Django | Experimental | ❌ Supabase | Experimental | ❌ n8n | Experimental | ❌ Ghost | Experimental | ❌ Laravel | Experimental | ❌ SvelteKit | Experimental | ❌ If you try importing a project with your preferred framework, we would love to know how your experience was and what we should improve or fix, so please let us know! --- ## Got Feedback or Issues? The Import Repository is still in beta overall, and your feedback helps us improve. If you have questions or encounter problems: - Join our [Discord community](https://discord.gg/vvgQxVjC8G) - Or email us directly at **** Give it a spin with your favorite project. 🙂‍↕️ [Try Import from GitHub today](https://console.diploi.com/) Happy deploying! --- ## References - Diploi Components - Custom Domains ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Nue.js, SvelteKit and MariaDB now available on Diploi 🎉 > We are happy to announce the new technologies that you can start deploying and develop... Javier April 14, 2025 [Read on Dev.to](https://dev.to/diploi/nuejs-sveltekit-and-mariadb-now-available-on-diploi-c5c) --- ###### We are happy to announce the new technologies that you can start deploying and develop using Diploi! --- ## Nue.js, SvelteKit and MariaDB now supported So as a development/deployment platform, something we frequently get asked is "do you support xyz technology?". We would love to say **YES** to all technologies we hear about, but that's not the reality yet 😑 BUT! That said, we are happy to officially add support for these three technologies. In case you are not aware of them, let's go over a brief intro for each one --- ### What is Nue.js? In their own words ( > Nue is a web framework focused on web standards, currently in active development. Our goal is to expose the hidden complexity that's become a norm in modern web development. When a single button weighs more than an entire application, something is clearly broken. > > Nue makes the inevitable shift. We're rebuilding the entire ecosystem from scratch, with a cleaner, more efficient core. Our goal is to restore the joy of web development for all key skillsets: frontend architects, design engineers, and UX engineers. In a nutshell, the Nue.js team created a lightweight framework to build single-page apps. How lightweight? Well, their benchmark says that a WHOLE single-page application with Nue.js is about 50% lighter than a SINGLE React button Yeah, I couldn't believe it either... To me, the best part (or worst for some) is the rediscovery (or horror) of model-view-controller aka MVC, applied to modern web development As a Rails lover here ✊ I agree with [their vision](https://nuejs.org/vision/) that basically says that we are constantly reinventing the wheel every time we launch a new app, and I believe that they are right, and using MVC avoids that, but I'm bias... You can try it yourself and decide if it is good for you --- ### What is SvelteKit? If you have worked with Next.js, SvelteKit will be very familiar for you SvelteKit is a fullstack framework that uses Svelte and adds the functionality necessary to build applications It features server-side rendering, static site generation, API endpoints, and file-based routing. SvelteKit bundles are lightweight and it is compatible with a very broad list of technologies, like Vite to enable hot module reloading for example You can try SvelteKit already on Diploi For more about Svelte and SvelteKit, check --- ### What is MariaDB? Created as a fork of MySQL, by the same people who created MySQL, as a way to keep a version of MySQL fully open-source after Oracle acquired MySQL. MariaDB is a fully open-source relational database, which operates for most purposes like MySQL The main difference with MySQL, can be found in the performance improvements introduced with dynamic thread pooling and the added support for other storage engines, so you are not limited only to SQL If you have used SQL before, you will find that MariaDB is quite straight forward to work with You can try MariaDB as an add-on to any of the technologies we support from our homepage To learn more about MariaDB, check their website --- We are now working on new components for Python and PHP, so we hope to have an update soon! Keep building friend! 🫡 --- #### [Try Diploi for free ✨](https://diploi.com/) --- **References:** \ \ \ ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # 7 Remote Development Platforms in 2025, to Code without a Local Setup > We discuss 7 remote development platforms that you can use in 2025 to code, run, and test applications in the cloud without the need for a local setup Javier June 10, 2025 Updated October 28, 2025 ###### If you code locally, probably you heard this at least once [Jump to the list of remote development platforms](#top-7-remote-development-platforms-in-2025) Or maybe your version of `node/python/` is too old or too new to run the application you are working on, so you need to install an additional tool to manage different versions of said tool When it is not an issue with the tooling necessary to run your application, it can be a config issue or environment variables missing Well, there are ways to avoid the additional work required to run an application locally. One example that blew my mind was how the team at OkTurtles handles all of their config, where you don’t need any `.env` files or special config for one of their very complex projects, [Group Income](https://github.com/okTurtles/group-income), where they put a lot of effort to make the process of onboarding new people and working collaboratively as seamless as possible Check their video about [how they handle passwords inside Group Income](https://www.youtube.com/watch?v=AaX28k9pJ8s) BUT… that was a lot of effort and time dedicated to making their product work as consistent as possible for all developers, regardless of the machine you are using So what about us? I don’t want to spend time doing that and chances are you neither… This leads me to introduce you to: --- ## Remote Development Environments Remote development environments are platforms that allow you to code, run, and test your applications in the cloud, eliminating the need for local setup and configuration. This means you can work from anywhere, on any device (even from your mobile browser although with limitations), without worrying about compatibility issues or missing dependencies The benefits of using remote development platforms include: - **Consistency**: Ensures that everyone on your team is using the same environment, reducing the “it works on my machine” problem - **Accessibility**: Access your development environment from any device with an internet connection, making it easier to work on the go - **Resource Management**: Offload resource-intensive tasks to the cloud, freeing up your local machine - **Collaboration**: Share your development environment with team members, making it easier to collaborate on projects - **Scalability**: Easily scale your development environment to handle larger projects or more complex applications - **Cost-Effective**: Many platforms offer free tiers or pay-as-you-go pricing, making it affordable for individuals and small teams - **Security**: Remote platforms often provide better security measures than local setups, protecting your code and data - **Environment Isolation**: Each project can have its isolated environment, preventing conflicts between dependencies - **Integrated Tools**: Many platforms come with built-in tools for version control, debugging, and deployment, streamlining your workflow There might be more benefits, but these are the ones I find most relevant for me. When I started working at Diploi, since our product supports remote development, I have been using it for all of my projects, specially for testing and experimenting with new ideas An example of this is how we use Diploi to develop and test changes to our documentation, where we create a project for our team to host our Docs, and then we can create multiple environments for each team member or feature we are working on This way I can start coding without running anything locally, and I can share my work with the team by just sharing the link to the project, which is hosted on Diploi For example, while writing this blog, I created a new remote development environment to show how it works in about 60 seconds: As you can see, no local setup is required. I simply created a new deployment, and I can start coding right away. But that’s not why you are here, you want to know which remote development platforms are available, so let’s get to it! --- ## Top 7 Remote Development Platforms in 2025 --- ### DevZero > “Ready-to-Code, Cost Efficient Dev Environment.” DevZero is a cloud-based development platform designed to provide developers with ready-to-code, production-like environments. By mirroring production setups, it aims to eliminate the common “it works on my machine” problem, ensuring consistency across development and deployment stages. DevZero leverages MicroVMs to offer isolated environments that dynamically scale resources, optimizing performance and cost Known as Workspace or DevBoxes in DevZero, these allow developers to create isolated, customizable environments for development, testing, and deployment. These environments are built dynamically from a predefined configuration file called a recipe, which specifies dependencies, tools, and resources. Each workspace is provisioned with its own Kubernetes cluster and can be launched in a region of the user’s choice. This approach ensures consistent environments for team members and supports demanding workloads like CI/CD pipelines and data processing. The next step for users is to create a workspace by selecting or configuring a recipe and launching it on the DevZero platform. #### IDE options supported To access and work within DevZero’s Workspaces, you can use JetBrains and VS Code with the Remote SSH extension. For either IDE, you will need to install the DevZero’s CLI to connect to your workspace #### Anything free? DevZero used to offer a free tier, but it seems that they have moved away from this model 🥲 #### Pricing? DevZero no longer showcases its pricing plans on its website, and the latest information available online comes from SaaSworthy which lists the following plans: **Starter Plan**: Allows up to 2 users per team and 2 workspaces per user - **Price**: $0/month **Pro Plan**: Includes custom roles, up to 15 users, 2 active workspaces per user, and 30 workspaces per team - **Price**: $39.95 per user per month **Growth Plan**: Offers storage volumes/buckets, integrations with existing infrastructure, up to 15 teams (max 15 users per team), administrative dashboards, usage controls/policies, and dedicated support SLA - **Price**: $429.95 per team per month **Enterprise Plan**: Provides self-hosted options, SSO support, external secret manager, APM, full RBAC, and dedicated support rep with SLA - **Price**: Custom pricing But keep in mind that these prices are not directly from DevZero’s website and were last updated on the 26th of August 2024, so they are probably not accurate anymore #### Something else? You can launch workspaces on DevZero in different regions. The region where a workspace is launched depends on the user’s team and subscription tier. Upon signing up, a default region is set, but users can change this preference in their user settings #### Video demo? --- ### Codeanywhere > “The AI Cloud IDE” Codeanywhere is a cross-platform cloud-integrated development environment (IDE) that enables users to write, edit, collaborate, and run web development projects directly from a web browser or mobile device. It supports over 75 programming languages, including HTML, JavaScript, Node.js, PHP, Ruby, Python, and Go The platform offers features such as real-time collaboration, version control integration with GitHub, GitLab, and Bitbucket, and the ability to connect to remote file systems via SFTP. Codeanywhere supports DevContainer.json for standardized workspace configurations which you can customize in multiple ways #### IDE options supported Codeanywhere provides a browser-based IDE powered by Visual Studio Code where you can import your own VS Code extensions, themes, and settings. Additionally, it offers AI-powered code completion and suggestions using the [Continue.dev](https://www.continue.dev/) extension #### Anything free? Codeanywhere offers a free tier with an allowance of 20 hours of use, so users can explore the platform before committing to a subscription #### Pricing? Codeanywhere has monthly, annual, and 2-year plans, with the following options: **Free Plan**: One-time usage with essential features for getting started - **Price**: $0 (one-time usage) **Basic Plan**: Ideal for growing teams with more flexibility and workspace options - **Price**: $12 monthly | $9.60 per member/month, billed annually | $8.40 per member/month, billed every 2 years **Premium Plan**: Maximum value for teams needing more resources and parallel workspaces - **Price**: $29 monthly | $23 per member/month, billed annually | $20 per member/month, billed every 2 years **Enterprise Plan**: Custom solutions for organizations with on-premise or cloud deployment need - **Price**: Custom pricing (contact sales) #### Something else? Codeanywhere supports on-premises deployment options, allowing users to host the platform within their own infrastructure. The platform is also SOC2 Type II, ISO 27001, and GDPR compliant, ensuring high standards of security and data protection #### Video demo? --- ### Coder > “Secure environments for developers and their agents” Coder is a self-hosted cloud development platform that allows you to code in the cloud without needing a local setup. The main use of Coder is to provide a way to launch and manage your virtual development environments from a single dashboard, without having to set up each environment manually You can define your development environments using templates, where you can launch remote development servers using Kubernetes or Docker, and then launch them from the Coder dashboard. Besides managing your environments, Coder also provides a way to code using their own open source IDE, Coder-server, or using your own IDE by connecting via SSH #### IDE options supported Officially supports VS Code, JetBrains IDEs, and their own web-based IDE #### Anything free? Coder is open‑source and allows you to self-host so you would only worry about the costs of your infrastructure. You can also start a Premium trial which has additional features intended for teams and enterprises #### Pricing? Coder is open source and it is available in two editions **Community**: Open-source edition, self-hosted, and free to use - **Price**: Free **Premium**: Paid edition with additional features such as global support, access controls, audit logging, workspace autoscaling and proxying, branding, and enterprise-grade governance - **Price**: Custom pricing #### Something else? As I mentioned before, Coder also has a web-based IDE called Coder-server which is based on VS Code. You can use it to code in the browser or to connect to your remote development environments via SSH #### Video demo? --- ### GitHub Codespaces > “Secure development made simple” GitHub Codespaces offers managed, container-based development environments hosted in the cloud. You can spin up a live VS Code environment on the browser, directly from any GitHub repo, complete with full terminal support These environments can be configured using DevContainer.json files, allowing project-specific setups with dependencies, tools, and custom init commands #### IDE options supported You can use the web-based VS Code IDE, and it also supports local VS Code instances via the GitHub Codespaces extension #### Anything free? Personal GitHub accounts receive 120 hours of free Codespaces usage per month and 15 GB of storage. Codespace hours are calculated based on the number of cores and the duration of usage. For example: - A 2-core machine used for 1 hour equals 2 core hours - An 8-core machine used for 1 hour equals 8 core hours - An 8-core machine used for 2 hours equals 16 core hours #### Pricing? Codespaces bills based on the number of core hours used and the storage consumed: **Codespaces compute (2 core)**: - **Price**: $0.18 per 1 hour **Codespaces compute (4 core)**: - **Price**: $0.36 per 1 hour **Codespaces compute (8 core)**: - **Price**: $0.72 per 1 hour **Codespaces compute (16 core)**: - **Price**: $1.44 per 1 hour **Codespaces compute (32 core)**: - **Price**: $2.88 per 1 hour **Codespaces storage**: Storage resource for Codespaces - **Price**: $0.07 per 1 GB-month #### Something else? Codespaces can be used for pull requests, allowing you to review and test changes in a live environment before merging #### Video demo? --- ### DevPod > Codespaces but… Open Source, Client Only, Unopinionated” 🌱 DevPod is an open‑source tool for creating reproducible development environments using the DevContainer standard. It connects your local IDE to workspaces running locally, in Kubernetes, or on any cloud provider DevPods run based on a `devcontainer.json`, to create consistent environments. You can use DevPod to run your development environments on your own infrastructure. It supports multiple IDEs and provides a CLI and GUI for managing workspaces #### IDE options supported DevPod supports VS Code Browser or Desktop, JetBrains IDEs, and connecting any IDE via SSH #### Anything free? DevPod is open source and free and uses your own infrastructure to run your workspaces, and only runs on your local machine #### Pricing? There seems to be no paid version for DevPod, which I think is because DevPod is part of a larger ecosystem of tools that Loft (creators of DevPod) use to provide tools for Virtualization and Kubernetes management #### Something else? DevPod provides a way to create CLI programs called Providers, that enable the creation, management, and running of user-requested workspaces. They support various backends, such as cloud services or container environments. There are two main types: **Machine providers**, which manage virtual machines (e.g., AWS Provider using EC2) **Non-Machine providers**, which work directly with containers (e.g., SSH, Kubernetes, or Docker) Provider configurations are defined in a `provider.yaml` file, and you can learn how to add or develop your own providers through DevPod’s documentation #### Video demo? --- ### Gitpod > “Productivity starts with your AI-ready development environment” Gitpod is a cloud development environment platform that delivers on-demand, fully automated workspaces based on pre-configured `devcontainer.json` files. These environments come ready-to-code with all required tools and dependencies, support any Git repository, and can run in the browser, locally via desktop, or self-hosted in private infrastructure Gitpod automates the setup of development environments, allowing developers to focus on coding rather than configuration. It supports multiple IDEs and provides features like prebuilds, which automatically prepare workspaces with the latest code changes, and ephemeral workspaces that can be spun up and down as needed #### IDE options supported Gitpod works with any editor that uses SSH to connect to a remote backend, which means it supports a wide range of IDEs and code editors, including VS Code, JetBrains IDEs (such as IntelliJ IDEA, PyCharm, and WebStorm), Cursor, Windsurf, Zed, and any other IDE that can use SSH to connect to a remote development environment #### Anything free? Gitpod has a free tier that allows you to run up to 10 development environments #### Pricing? Gitpod has three tiers: **Free**: Best for individuals and testing the waters - **Price**: Free **Core**: Coming soon, best for heavy users and small teams - **Price**: Not yet available **Enterprise**: Best for large organizations with additional compliance requirements - **Price**: Custom pricing #### Something else? Gitpod provides an SDK that allows developers to interact programmatically with Gitpod environments for automation and infrastructure management. It supports Python, Node/Typescript, and Go #### Video demo? --- ### Diploi > “Magical Developer Experience” Diploi is a development and deployment platform that enables developers to spin up full-stack applications quickly and simplifies both development and deployments by reducing the configuration required to launch environment online You can launch a new development environment for an application in seconds, with the ability to start coding in the browser or connecting your own IDE via SSH. Diploi focuses on simplifying the developer experience by automating infrastructure management, deployments, and CI/CD pipelines Using a visual stack builder, developers select components (e.g., Next.js, Astro, Node/Bun) and services (PostgreSQL, Redis, MongoDB) to generate a preconfigured monorepo and deployment setup, which you can try out yourself without signing up by visiting [diploi.com/#StackBuilder](https://diploi.com/#StackBuilder) #### IDE options supported Using Diploi you can start coding in the browser using our implementation of Code-server to code in browser and we also support VS Code and Cursor out of the box, or if you use another IDE, you can connect via SSH #### Anything free? Diploi offers €50 free credits upon signup to explore and experiment with the platform #### Pricing? Diploi operates on a pay-as-you-go model, with no fixed monthly fees. You only pay for the time your environments are active and the size of the cluster you use for your deployments: **Diploi Cluster (S)**: 2 vCPUs, 4 GB RAM - **Price**: €0.026 per 1 hour **Diploi Cluster (M)**: 2 vCPUs, 8 GB RAM - **Price**: €0.048 per 1 hour **Diploi Cluster (L)**: 4 vCPUs, 16 GB RAM - **Price**: €0.089 per 1 hour **Diploi Cluster (XL)**: 8 vCPUs, 32 GB RAM - **Price**: €0.182 per 1 hour **Diploi Storage**: Persistent storage for your deployments - **Price**: €0.002 per 1 GB-hour #### Something else? Diploi has a way to define environments using a `diploi.yaml` file which contains the configuration to build infrastructure for a deployment. It defines components and add-ons, each with a name, unique identifier, package URL, and version. The file allows for importing environment variables from other components, which can be remapped or filtered using wildcards #### Video demo? Here’s a quick intro to using Diploi: --- ## Choosing the Right Platform What remote development platform works best, depends on your specific needs, stack, and budget. Here’s a quick summary to help you decide: - **Diploi:** Best for developers who not only want to code without local setup but also want a simplified deployment process for their application’s lifecycle, especially if you want to launch full-stack applications quickly with minimal configuration - **DevZero:** Best for teams needing production-like environments with dynamic scaling and isolated workspaces, especially if you want to self-host - **Codeanywhere:** Best for those who want a cross-platform cloud IDE with real-time collaboration and version control integration, especially if you want to use AI-powered code completion - **Coder:** Best for teams looking for a self-hosted solution to manage their own development environments with full control over configurations and IDE options - **GitHub Codespaces:** Best for developers who want seamless integration with GitHub and prefer using VS Code in the browser or locally, especially if you want to use pre-configured devcontainers - **DevPod:** Best for those who want an open-source, client-only solution to create reproducible development environments using DevContainer standards, especially if you want to self-host or run locally - **Gitpod:** Best for teams needing fully automated, ephemeral workspaces with prebuilds and support for multiple IDEs, especially if you want to use a wide range of IDEs and code editors --- Do you have a favorite remote development platform? Or maybe you are using one that is not listed here? Let me know in the comments --- In case you are curious, [Test-drive Diploi ✨](https://diploi.com/), no registration required --- **References:** - [DevZero](https://www.devzero.io/) - [Codeanywhere](https://codeanywhere.com/) - [Coder](https://coder.com/) - [GitHub Codespaces](https://github.com/features/codespaces) - [DevPod](https://devpod.sh/) - [Gitpod](https://www.gitpod.io/) - [Diploi](https://diploi.com/) - [OkTurtles Group Income](https://groupincome.org/) ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Remote Development Environments with Cursor? > Now you can connect to your remote development environments on Diploi using Cursor ... Javier May 6, 2025 [Read on Dev.to](https://dev.to/diploi/remote-development-with-cursor-4okl) --- ###### Now you can connect to your remote development environments on Diploi using Cursor ###### Diploi is a deployment platform for applications with support for remote development --- ## Vibing on Diploi ✨ We just added support for Cursor, which means that now you can start coding your application without installing anything locally and vibe your way to production --- ### How it works? **Don't want to read?** Check the video demo **If you prefer reading,** let's go step by step: **If you have a development environment already created, [you can skip to step 2](#step2)** #### 1. Create a project You can launch the project creation page from your dashboard's project page /projects Now choose the stack for your application. For this guide, I'll select Bun and Nue.js with Postgres for my demo app After clicking on `Launch Stack`, the Diploi creates a development deployment by default, but just in case I'll show how you can create a development deployment for our application ##### Creating a development deployment From your project page, click the `Create Deployment` button Select **Development**, which will allow you to start developing your app without having to run anything locally We recommend you use size M for your development environments, since the remote development environment will need additional resources to run your application in development mode After you finish configuring your development deployment, your new environment will start #### 2. Connect to your development deployment using Cursor Now that your deployment is configured and starting, you will be able to connect remotely when the button `Code in the Browser` inside the **Develop** section of your deployment changes from gray to blue You might be thinking, "that's not connect to Cursor" and you are right, all you need to do is click on the plus `+` next to `Code in the Browser`, which will open a dropdown where you can select to open your development environment with Cursor > If you have issues connecting, it might be due to missing SSH keys. Follow this guide explaining how to add a new SSH key to your Diploi account In case you prefer to make "Open in Cursor" a default action for your deployment, you can click on the pin "📌" icon, to pin it on your **Develop** section And now you should be able to open your deployment with Cursor and vibe out your app without having to install anything locally 💎 **If you don't have a Diploi account, you can still try launching a server for free, no registration needed** --- If you have been using Diploi for a while, you might notice that we updated our deployment page UI. We'll talk about our design process in another post That's all for now! Go out there and vibe friend 🪄 --- #### [Try Diploi for free ✨](https://diploi.com/) --- **References:** \ ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Setting up an application with Nue.js > This is a tutorial, walking through how to set your app with Nue.js By the end of this... Javier April 25, 2025 [Read on Dev.to](https://dev.to/diploi/setting-up-an-application-with-nuejs-3261) ###### This is a tutorial, walking through how to set your app with Nue.js --- By the end of this tutorial, we will have a blank application, without any unnecessary packages, ready for you to create an application using Nue.js This will be part of a series we'll go deeper into what you can do with Nue.js and show practical tutorials --- ## What's Nue.js? Nue.js is a framework, that tries to simplify how applications are built and improve performance, by allowing the usage of faster languages so you are not limited by the typical performance of a JS application From their docs: \| Nue is a web framework that prioritizes web standards, enabling developers to create large-scale single-page applications (SPAs) with less code than mainstream tools require, and your codebase stays clean so it is easier to maintain and scale. After trying Nue.js, I can say this is a JS framework with good ideas. It creates very light bundle sizes, provides server-side rendering, allows writing application logic in Rust, Go or Zig for performance-critical tasks. Its model-view-controller (MVC) architecture can help maintain a structured development --- ## Requirements To install Nue, you must first have Bun installed in your system --- ### Install Bun To run Nue.js we will use Bun\ `curl -fsSL https://bun.sh/install | bash` You can use npm, yarn or pnpm too, for more info check --- ### Setting the project Now we need to create a folder to store our code,\ `mkdir nue-app` --- ### (Optional) Start an empty Bun project Then `cd` into your new folder and run the command\ `bun init` to create your base application, you will see this prompt: ``` ? Select a project template - Press return to submit. ❯ Blank React Library ``` Choose `Blank` and once bun finishes setting up your project, your root folder should look like this: ``` $ ls bun.lock index.ts node_modules package.json README.md tsconfig.json ``` --- ### Install Nue.js locally Now run the command\ `bun install nuekit` to install Nue.js in your project --- ### Create a site.yaml and index.html In the root of your application, create a site.yaml and index.html. The site.yaml file will tell Nue how to bundle and run our application while index.html will be the root view of our application ``` title: Nue CRM / A single-page app demo port: 8083 ``` ```

Hello World

``` --- ### Run the app in development Now you can run your Nue.js application, using the command:\ `bun nue` and that's it You should be able to see your application on `localhost:8083` and now you can start developing **NOTE**\ If you want to get a sample application running and skip this entire tutorial, just run:\ `bun nue create simple-blog` to create a blog sample or\ `bun nue create simple-mpa` to create a multipage sample app, with login and dashboard In case you want to create and deploy a Nue.js application with ease, try [Diploi's Nue.js component](https://diploi.com/component/nue), so you can have your app live online in seconds --- ## Closing thoughts I initially planned to make this into a single blog post, but after 3 days of trying to make sense of my experience learning Nue.js to make this blog, I realized that I was being naive and wouldn't be possible, so I split it into multiple parts This is just an introduction to Nue.js and in our next entry, we'll go over setting up the folder structure and logic for our application If you prefer to take the lead, check Nue's documentation about how to use Nue with [content-driven applications](https://nuejs.org/docs/content-focused-apps.html) and [single page apps](https://nuejs.org/docs/single-page-apps.html) --- We are working on new components, UX improvements and we'll be posting an update soon! Happy building! 🫡 --- #### [Try Diploi for free ✨](https://diploi.com/) --- **References:** \ ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Why we don't use an ORM and why you (probably) shouldn't > Jump to TLDR? > This post is mainly intended for coders early in their careers, ✨vibe... Javier March 26, 2025 [Read on Dev.to](https://dev.to/diploi/why-we-dont-use-an-orm-and-why-you-probably-shouldnt-4cfo) [Jump to TLDR? >](#tldr) --- ###### This post is mainly intended for coders early in their careers, ✨_vibe coders_✨ and anyone using an ORM just because --- ## We do not use ORMs We have tried all kinds of ORMs and in the end they have all proven to be a hindrance. Our recommendation: Bite the bullet, learn your SQL and as a bonus, you will have a skill that lasts for life. ORMs add a layer of abstraction that will give you all kinds of nightmares Now, I imagine, if you use ORMs regularly, your blood pressure went up a tiny bit, so I'll add a caveat here: If you are working on somewhat simple applications, without unusual reads and/or writes, sure! Writing `SELECT FROM ` for every case when you need to query/insert/delete/patch some data seems silly, we recognize that That's why in our specific case, where we do quite advanced SQL, process lots of logs and manage a diverse range of resources for our clients, we can't afford to: - Learn the ins and outs of ORMs - Rely on the performance promised by ORMs - Trust that the ORM we choose is as safe or that it will be maintained as the underlying query language would If you use an ORM, I would bet that there's a chance that it is because you saw `` using said ORM and you thought "Ah! This sponsored product will make me better!" Was that the case? 🤨 If that was your reason to use XYZ ORM, that's ok, I myself learned Haskell for a few hours because ThePrimeagen said it's the future, I wasn't aware it was a meme... so no shaming here friend, I'm just building awareness, that ORMs are not it 😊 --- ### Conclusion Hopefully, my bias rant above doesn't imply that "ORM bad", because they are not, but they aren't a "better" replacement for the native query language of your database I'll leave you with a few points you should ponder about if you lean towards using an ORM in your application: --- #### Database read/write security By having plain query language, you have no 'magic' behaviors, which facilitates audits and removes dependency on external libraries and tooling, which could introduce vulnerabilities through your ORM of choice If you plan on getting your application audited or apply for security certifications, using ORMs will make the already painful process, much more painful --- #### Debugging and scalability Using ORMs obfuscates debugging since you rely on the ORM to interact with your database and complicates how your application scales As queries grow in complexity, you can find yourself running operations through an ORM, which can have unexpected behaviors through the abstractions they offer, so if an exception is thrown, you will need to become familiar with the ORM's inner workings, on top of knowing the underlying query language In our opinion, it's better to dedicate your effort to the native language of your database (which is already A LOT) rather than spending more time figuring out how to do the same work through the ORM abstractions --- #### Portability Abstracting how you query/insert your database to be able to change easily to a new database is naive at best In reality, once your app complexity grows, your database will do too, so you can use whatever database-agnostic ORM to move your application from one database to another, but that doesn't mean you will be able to just "switch" without doing any rewriting to your database queries Sure, let's say you move from psql to MariaDB, your ORM might do well enough and you might not have to do any rewriting, but, if you are moving to a different database, chances are that if you will be changing to a entirely different paradigm than you current database logic, in which case using an ORM will obscure the transition and give you more headaches when porting your current database logic Using an ORM for 'portability' does not mean you are guaranteed a free lunch --- Let me be clear again, it is ok to use an ORM, but in a time when ✨_vibe coding_✨ has (forcibly) become a thing, you should be aware of this \~20 year old discussion about ORMs and what you are risking in the pursuit of convenience --- ### TLDR ORM's abstractions can wreck your life so be cautious No ORM will beat learning about your database's paradigm and their base query language, rather than relying on an abstraction --- Have a great day ✌ --- **References:** ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # A Year In Review > As we reflect on the journey we've taken this year, it’s clear that 2024 has been an incredible one for Diploi. Tuomas December 30, 2024 Updated October 28, 2025 As we reflect on the journey we’ve taken this year, it’s clear that 2024 has been an incredible one for Diploi. We kicked off the year with excitement, fresh from pitching Diploi to a group of investors at a Pitch Finland event, hosted by [FiBAN](https://fiban.org/). Inspired, we were ready to work toward securing our initial pre-seed funding round. At the time, the MVP version of Diploi was available for anyone to try, allowing us to gather valuable insights from early users. Some of our first users went above and beyond, providing extensive feedback and ideas. We’re incredibly grateful to them for their support and enthusiasm, thank you for being amazing! --- In May, a standout moment for us was presenting Diploi at a [HelsinkiJS](https://helsinkijs.org/) meeting, held at Finnair’s headquarters near Helsinki Airport. It was great to meet like-minded professionals, discuss how development and test environments can be more effectively managed and what Diploi brings to the table. As summer approached, we successfully brought together a group of investors and began officially securing our pre-seed funding, [which was formally announced in September](/blog/diploi-received-pre-seed-funding). This was an important milestone, as it provided the resources we needed to transform Diploi from an MVP into a fully working product. --- With funding secured, we got straight into development, while [publishing a roadmap](https://dev.to/diploi/diploi-roadmap-for-2024-1nde) and sharing technical blog posts about our philosophy and methods. We also made the decision to fully commit to the _config in code_ convention and shared a [preview of our implementation](https://dev.to/diploi/how-we-solved-infrastructure-as-code-2ldn). In November, we attended [Slush](https://slush.org/) as a startup and had the opportunity to meet with some incredible people! We’re excited to see you all again next year! And as the new year approaches, we’re shifting our focus to the future. Our goal is to launch the next version of Diploi for testing early in the year, with a full release to follow later on. So stay tuned! --- We want to thank you all for being a part of this exciting year for Diploi, and we look forward to seeing you again next year! Happy New Year ✨🥂 ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) --- # Launch Astro with > Launch a new Astro project with add-ons and you will instantly have access to a development environment. No registration required. Launch a new Astro project and you will instantly have access to a development environment. No sign-up required. - Astro - TypeScript - Node.js adapter [GitHub](https://github.com/diploi/component-astro) ### Something extra? Choose some optional add-ons to launch with Astro PostgreSQL 9 116 \[ ] Redis 1 450 \[ ] MongoDB 1 347 \[ ] MariaDB 1 245 \[ ] MinIO 385 \[ ] Launch Astro Instant launch. No sign-up required. --- Readme # Astro Component for Diploi Launch a trial, no registration needed Uses the official [node](https://hub.docker.com/_/node) Docker image. Has the [@astrojs/ node](https://docs.astro.build/en/guides/integrations-guide/node/) adapter preconfigured. ## Operation ### Getting started 1. **Sign up** at `https://console.diploi.com/` using your GitHub account. 1. In your dashboard, click **Create Project +** 1. Under **Pick Components**, choose **Astro**\ If you want to expand your Astro website with other tools, like a backend framework, here you can add them. 1. In **Pick Add-ons**, select any databases or tools supported on Diploi. 1. In **Repository**, choose **Create Repository** which will generate a new GitHub repo for you. 1. Click **Launch Stack** Prefer the full guide? Check ### Development Will run `npm install` when component is first initialized, and `npm run dev` when deployment is started. ### Production Will build a production ready image. Image runs `npm install` & `npm build` when being created. Once the image runs, `npm start` is called. ## Link - [Adding Astro to a project](https://docs.diploi.com/building/components/astro) - [Astro docs](https://docs.astro.build/en/getting-started/) --- ## What is Diploi? Diploi is the single SaaS service for managing, developing and hosting your full application. - ### Consistent - Consistent environments from development to production - Adoptable incrementally - start easy, grow later - ### One-Click - Fast 30 second new developer onboarding - One-click environment setup - Instantly shareable testing environments - ### Zero-Install - Zero-install remote development - Versatile support for any stack pre-build or custom [Learn more](/) --- # Launch Bun with > Launch a new Bun project with add-ons and you will instantly have access to a development environment. No registration required. Launch a new Bun project and you will instantly have access to a development environment. No sign-up required. - Generic - Bun - TypeScript [GitHub](https://github.com/diploi/component-bun) ### Something extra? Choose some optional add-ons to launch with Bun PostgreSQL 9 116 \[ ] Redis 1 450 \[ ] MongoDB 1 347 \[ ] MariaDB 1 245 \[ ] MinIO 385 \[ ] Launch Bun Instant launch. No sign-up required. --- Readme # Bun Component for Diploi Launch a trial, no card or registration required A generic Bun component that can be used to run any JS / TS app. Uses the official [oven/bun](https://hub.docker.com/r/oven/bun) Docker image. ## Operation ### Getting started 1. In the Dashboard, click **Create Project +** 1. Under **Pick Components**, choose **Bun** You can add other frameworks from this page if you want to create a monorepo application, eg, Bun for API + React for frontend. 1. In **Pick Add-ons**, select any databases you need. 1. Choose **Create Repository**, which will generate a new GitHub repo. 1. Finally, click **Launch Stack** Link the guide ### Development Will run `bun install` when component is first initialized, and `bun dev` when deployment is started. ### Production Will build a production ready image. Image runs `bun install` & `bun run build` when being created. Once the image runs, `bun start` is called. ## Links - [Adding Bun to a project](https://docs.diploi.com/building/components/bun) - [Bun documentation](https://bun.sh/docs) --- ## What is Diploi? Diploi is the single SaaS service for managing, developing and hosting your full application. - ### Consistent - Consistent environments from development to production - Adoptable incrementally - start easy, grow later - ### One-Click - Fast 30 second new developer onboarding - One-click environment setup - Instantly shareable testing environments - ### Zero-Install - Zero-install remote development - Versatile support for any stack pre-build or custom [Learn more](/) --- # Launch Deno with > Launch a new Deno project with add-ons and you will instantly have access to a development environment. No registration required. Launch a new Deno project and you will instantly have access to a development environment. No sign-up required. - Deno - TypeScript - JSX & TSX [GitHub](https://github.com/diploi/component-deno) ### Something extra? Choose some optional add-ons to launch with Deno PostgreSQL 9 116 \[ ] Redis 1 450 \[ ] MongoDB 1 347 \[ ] MariaDB 1 245 \[ ] MinIO 385 \[ ] Launch Deno Instant launch. No sign-up required. --- Readme # Deno Component for Diploi A generic Deno component that can be used to run any Deno app. Uses the official [Deno](https://hub.docker.com/r/denoland/deno) Docker image. ## Operation ### Getting started 1. In the Dashboard, click **Create Project +** 1. Under **Pick Components**, choose **Deno** 1. In **Pick Add-ons**, you can add one or multiple databases to your app 1. Choose **Create Repository**, which will generate a new GitHub repo 1. Lastly, click **Launch Stack** Link to guide, explains how to add a custom domain and launch to production ### Development Runs `deno task dev` when deployment is started, which executes your app in watch mode with network and environment variable access: ```sh deno run --watch --allow-net --allow-env src/main.ts ``` No `deno install` is required, as new import in TypeScript files will trigger Deno to automatically download and cache those modules as needed. ### Production Builds a production-ready image. Runs `deno task prod` to start your app with network and environment variable access: ```sh deno run --allow-net --allow-env src/main.ts ``` Dependencies are cached during the build stage using `deno cache .`. ## Links - [Adding Deno to a project](https://docs.diploi.com/building/components/deno) - [Deno documentation](https://docs.deno.com/runtime/) --- ## What is Diploi? Diploi is the single SaaS service for managing, developing and hosting your full application. - ### Consistent - Consistent environments from development to production - Adoptable incrementally - start easy, grow later - ### One-Click - Fast 30 second new developer onboarding - One-click environment setup - Instantly shareable testing environments - ### Zero-Install - Zero-install remote development - Versatile support for any stack pre-build or custom [Learn more](/) --- # Launch Django with > Launch a new Django project with add-ons and you will instantly have access to a development environment. No registration required. Launch a new Django project and you will instantly have access to a development environment. No sign-up required. - Django - Python - Pip [GitHub](https://github.com/diploi/component-django) ### Something extra? Choose some optional add-ons to launch with Django PostgreSQL 9 116 \[ ] Redis 1 450 \[ ] MongoDB 1 347 \[ ] MariaDB 1 245 \[ ] MinIO 385 \[ ] Launch Django Instant launch. No sign-up required. --- Readme # Django Component for Diploi Start a demo, no card required Getting started guide A generic Django component ready to build your Django app. This component was kickstarted running `django-admin startproject djangoapp` and it has `DEBUG=true` inside **settings.py** by default **To secure your Django app,** you must **update your SECRET\_KEY in settings.py** By default all Django apps use SQlite, which you must update to use your database of choice inside **settings.py** Uses the official [astral-sh/uv:3.13-alpine](https://github.com/astral-sh/uv/pkgs/container/uv) Docker image and Django #### IMPORTANT - You must generate a new SECRET\_KEY for your own application - Remember to update the database settings inside **settings.py** to match your own database config - In production you must remember to update your **settings.py**, by changing `DEBUG=false` and if you want to use external CDNs for your static files, you will need to update the `STATIC_ROOT` - For production and development, you are free to change the app server runner, so for example, if you prefer `uwsgi` you can change it directly on the Dockerfile for production and development - To install new packages, this component uses `uv`, so you can add new packages using `uv add ` ## Operation ### Getting started 1. In the Dashboard, click **Create Project +** 1. Under **Pick Components**, choose **Django** 1. In **Pick Add-ons**, you can add one or multiple databases to your app 1. Choose **Create Repository**, which will generate a new GitHub repo 1. Now click **Launch Stack** ### Development Will run `uv sync` when component is first initialized, and `uv run --isolated python3 manage.py runserver 0.0.0.0:8000` when deployment is started. ### Production Will build a production ready image. The first step runs the command: `uv sync --locked --no-dev --group deploy` Which installs **gunicorn**, as part of `--group=deploy` in `pyproject.toml`, to install all necessary dependencies for production. To get all static files, the image runs the command: `uv run --locked --no-dev python manage.py collectstatic --noinput` to get all static files. Lastly, the image will start the production server with the command: `uv run gunicorn djangoapp.wsgi:application --bind 0.0.0.0:8000 --workers 3 --log-level info` ## Links - [Adding Django to a project](https://docs.diploi.com/building/components/django) - [Django for production](https://docs.djangoproject.com/en/5.2/howto/deployment/checklist/) - [Django static files](https://docs.djangoproject.com/en/5.2/howto/static-files/) - [SECRET\_KEY in Django](https://docs.djangoproject.com/en/5.2/ref/settings/#std-setting-SECRET_KEY) - [Databases in Django](https://docs.djangoproject.com/en/5.2/ref/databases/) - [Working with multiple databases in Django](https://docs.djangoproject.com/en/5.2/topics/db/multi-db/) --- ## What is Diploi? Diploi is the single SaaS service for managing, developing and hosting your full application. - ### Consistent - Consistent environments from development to production - Adoptable incrementally - start easy, grow later - ### One-Click - Fast 30 second new developer onboarding - One-click environment setup - Instantly shareable testing environments - ### Zero-Install - Zero-install remote development - Versatile support for any stack pre-build or custom [Learn more](/) --- # Launch FastAPI with > Launch a new FastAPI project with add-ons and you will instantly have access to a development environment. No registration required. Launch a new FastAPI project and you will instantly have access to a development environment. No sign-up required. - FastAPI - Python - Uvicorn [GitHub](https://github.com/diploi/component-fastapi) ### Something extra? Choose some optional add-ons to launch with FastAPI PostgreSQL 9 116 \[ ] Redis 1 450 \[ ] MongoDB 1 347 \[ ] MariaDB 1 245 \[ ] MinIO 385 \[ ] Launch FastAPI Instant launch. No sign-up required. --- Readme # FastAPI Component for Diploi ## Operation ### Getting started 1. In the Dashboard, click **Create Project +** 1. Under **Pick Components**, choose **FastAPI**. Here you can also add a frontend framework to create a monorepo app, eg, FastAPI for backend and React+Vite for frontend 1. In **Pick Add-ons**, you can add one or multiple databases to your app 1. Choose **Create Repository** to generate a new GitHub repo 1. Finally, click **Launch Stack** Link to the full guide ### Development During development, the container installs Node.js and `nodemon` to enable automatic reloads when files change. The development server is started with: ```sh nodemon --delay 1 --watch pyproject.toml --watch ".venv/lib/*" --watch ".venv/lib64/*" --exec "uv run --isolated uvicorn src.main:app --host 0.0.0.0 --port 8000 --reload --reload-dir src --reload-exclude \".venv/**\"" ``` This will: - Use nodemon to watch for changes to pyproject.toml and restart the server when changes are detected. - Run the command uv run —isolated uvicorn src.main:app —host 0.0.0.0 —port 8000 —reload in an isolated Python environment. - Start the FastAPI app using uvicorn on all network interfaces at port 8000. - Enable hot-reload via uvicorn —reload, so the server automatically restarts when Python source files change. ### Production Builds a production-ready image. During the build, dependencies are installed with `uv sync`. When the container starts, it runs: ```sh fastapi run src/main.py --proxy-headers --port 8000 ``` This uses the FastAPI CLI to serve your application on port 8000. ## Links - [Adding FastAPI to a project](https://docs.diploi.com/building/components/fastapi) - [FastAPI documentation](https://fastapi.tiangolo.com/) - [Python documentation](https://docs.python.org/) - [uv documentation](https://docs.astral.sh/uv/) --- ## What is Diploi? Diploi is the single SaaS service for managing, developing and hosting your full application. - ### Consistent - Consistent environments from development to production - Adoptable incrementally - start easy, grow later - ### One-Click - Fast 30 second new developer onboarding - One-click environment setup - Instantly shareable testing environments - ### Zero-Install - Zero-install remote development - Versatile support for any stack pre-build or custom [Learn more](/) --- # Launch Flask with > Launch a new Flask project with add-ons and you will instantly have access to a development environment. No registration required. Launch a new Flask project and you will instantly have access to a development environment. No sign-up required. - Flask - Python - Gunicorn [GitHub](https://github.com/diploi/component-flask) ### Something extra? Choose some optional add-ons to launch with Flask PostgreSQL 9 116 \[ ] Redis 1 450 \[ ] MongoDB 1 347 \[ ] MariaDB 1 245 \[ ] MinIO 385 \[ ] Launch Flask Instant launch. No sign-up required. --- Readme # Flask Component for Diploi ## Operation ### Getting started 1. In the Dashboard, click **Create Project +** 1. Under **Pick Components**, choose **Flask**. Here you can also add a frontend framework to create a monorepo app, eg, Flask for backend and React+Vite for frontend 1. In **Pick Add-ons**, you can add one or multiple databases to your app 1. Choose **Create Repository** to generate a new GitHub repo 1. Finally, click **Launch Stack** Full guide at ### Development During development, the container installs Node.js and `nodemon` to enable automatic reloads when files change. The development server is started with: ```sh nodemon --delay 1 --watch "pyproject.toml" --watch ".venv/lib/*" --watch ".venv/lib64/*" --watch "src" --ext "py" --exec "uv run --isolated flask --app src/main.py run --host=0.0.0.0 --port=8000 --no-reload --debug" ``` This will: - Activate the virtual environment in `.venv` - This runs the Flask app defined in main.py using the uv tool in an isolated environment, making the app available on all network interfaces at port 8000, with debug mode enabled. ### Production Builds a production-ready image. During the build, dependencies are installed with `uv sync`. When the container starts, it runs: ```sh uv run --frozen gunicorn -w 4 -b 0.0.0.0:8000 src.main:app ``` This uses the Gunicorn to serve your application on port 8000. ## Links - [Adding Flask to a project](https://docs.diploi.com/building/components/flask) - [Flask documentation](https://flask.palletsprojects.com/en/stable/) - [Python documentation](https://docs.python.org/) - [uv documentation](https://docs.astral.sh/uv/) --- ## What is Diploi? Diploi is the single SaaS service for managing, developing and hosting your full application. - ### Consistent - Consistent environments from development to production - Adoptable incrementally - start easy, grow later - ### One-Click - Fast 30 second new developer onboarding - One-click environment setup - Instantly shareable testing environments - ### Zero-Install - Zero-install remote development - Versatile support for any stack pre-build or custom [Learn more](/) --- # Launch Ghost with > Launch a new Ghost project with add-ons and you will instantly have access to a development environment. No registration required. Launch a new Ghost project and you will instantly have access to a development environment. No sign-up required. - Website builder - Content editor - Subscriber management [GitHub](https://github.com/diploi/component-ghost) ### Something extra? Choose some optional add-ons to launch with Ghost PostgreSQL 9 116 \[ ] Redis 1 450 \[ ] MongoDB 1 347 \[ ] MariaDB 1 245 \[ ] MinIO 385 \[ ] Launch Ghost Instant launch. No sign-up required. --- Readme # Ghost Component for Diploi Start with a free trial, no account required Run [Ghost](https://ghost.org/) on Diploi. Uses the official [ghost](https://hub.docker.com/_/ghost/) Docker image. ## Operation Includes custom storage adapters for Diploi. These save images, files and media to a storage volume that will persist between reboots. This volume can be found at `/data` on the Ghost `app` container. ### Getting started 1. **Sign up** for Diploi at `https://console.diploi.com/` using your GitHub account. 1. In your dashboard, click **Create Project +** 1. Under **Pick Components**, choose **Ghost**\ If you want to expand your Ghost blog with other tools, like a backend framework to add an API, in this section, you can add them. They will all be hosted on a single server, reducing costs and complexity. 1. In **Pick Add-ons**, select any databases or tools you want to include. 1. In **Repository**, choose **Create Repository** which will generate a new GitHub repo for you. 1. Click **Launch Stack** Check the full guide ### Development When running a development environment, Ghost will be run in development mode too. This will allow you to develop custom themes and plugins with ease. To learn more about developing on Ghost, see the [Developing Themes](https://ghost.org/docs/install/local/#developing-themes) section of their docs. ### Production The production image will be an optimized, minimal version with your custom code baked in. Depending on which features you have been working on, you might have to apply them in the Ghost Admin panel (like themes and plugins). ## Links - [Adding Ghost to a project](https://docs.diploi.com/building/components/ghost) - [Ghost documentation](https://ghost.org/docs/) --- ## What is Diploi? Diploi is the single SaaS service for managing, developing and hosting your full application. - ### Consistent - Consistent environments from development to production - Adoptable incrementally - start easy, grow later - ### One-Click - Fast 30 second new developer onboarding - One-click environment setup - Instantly shareable testing environments - ### Zero-Install - Zero-install remote development - Versatile support for any stack pre-build or custom [Learn more](/) --- # Launch Hono with > Launch a new Hono project with add-ons and you will instantly have access to a development environment. No registration required. Launch a new Hono project and you will instantly have access to a development environment. No sign-up required. - Hono - Bun - Ultrafast & lightweight [GitHub](https://github.com/diploi/component-hono) ### Something extra? Choose some optional add-ons to launch with Hono PostgreSQL 9 116 \[ ] Redis 1 450 \[ ] MongoDB 1 347 \[ ] MariaDB 1 245 \[ ] MinIO 385 \[ ] Launch Hono Instant launch. No sign-up required. --- Readme # Hono Component for Diploi Start a free demo without registering an account Run [Hono](https://hono.dev/) on Diploi. Uses [Bun](https://bun.sh/) to handle dependencies and to run the application. Uses the official [oven/bun](https://hub.docker.com/r/oven/bun) Docker image. ## Operation ### Getting started 1. **Sign up** for a free Diploi account at 1. In the Dashboard, click **Create Project +** 1. Under **Pick Components**, choose **Hono** You can add other frameworks from this page. 1. In **Pick Add-ons**, select any databases or extra tools you need. 1. Choose **Create Repository** so Diploi generates a new GitHub repo for your project. 1. Click **Launch Stack** Link to guide ### Development Will run `bun install` when component is first initialized, and `bun dev` when deployment is started. ### Production Will build a production ready image. Image runs `bun install` & `bun run build` when being created. Once the image runs, `bun start` is called. ## Links - [Adding Hono to a project](https://docs.diploi.com/building/components/hono) - [Hono documentation](https://hono.dev/docs/) - [Bun documentation](https://bun.sh/docs) --- ## What is Diploi? Diploi is the single SaaS service for managing, developing and hosting your full application. - ### Consistent - Consistent environments from development to production - Adoptable incrementally - start easy, grow later - ### One-Click - Fast 30 second new developer onboarding - One-click environment setup - Instantly shareable testing environments - ### Zero-Install - Zero-install remote development - Versatile support for any stack pre-build or custom [Learn more](/) --- # Launch Laravel with > Launch a new Laravel project with add-ons and you will instantly have access to a development environment. No registration required. Launch a new Laravel project and you will instantly have access to a development environment. No sign-up required. - Laravel - FrankenPHP - PHP 8 [GitHub](https://github.com/diploi/component-laravel) ### Something extra? Choose some optional add-ons to launch with Laravel PostgreSQL 9 116 \[ ] Redis 1 450 \[ ] MongoDB 1 347 \[ ] MariaDB 1 245 \[ ] MinIO 385 \[ ] Launch Laravel Instant launch. No sign-up required. --- Readme # Laravel Component for Diploi Launch a trial, no account needed Uses the official [FrankenPHP](https://hub.docker.com/r/dunglas/frankenphp) Docker image. ## Operation ### Getting started 1. In the Dashboard, click **Create Project +** 1. Under **Pick Components**, choose **Laravel (PHP)** You can add other frameworks from this page if you want to create a monorepo application, eg, Laravel + (React + Vite for frontend). 1. In **Pick Add-ons**, select any databases or extra tools you need. 1. Choose **Create Repository** so Diploi generates a new GitHub repo for your project. 1. Click **Launch Stack** Check the guide ### Development Will run `composer install --optimize-autoloader --no-interaction` when component is first initialized, and `frankenphp php-server` when deployment is started. ### Production Will build a production ready image. Image runs `composer install --no-dev --optimize-autoloader --no-interaction` when being created. Once the image runs, `frankenphp php-server` is called. ## Links - [Adding Laravel to a project](https://docs.diploi.com/building/components/laravel) - [Laravel documentation](https://laravel.com/docs) --- ## What is Diploi? Diploi is the single SaaS service for managing, developing and hosting your full application. - ### Consistent - Consistent environments from development to production - Adoptable incrementally - start easy, grow later - ### One-Click - Fast 30 second new developer onboarding - One-click environment setup - Instantly shareable testing environments - ### Zero-Install - Zero-install remote development - Versatile support for any stack pre-build or custom [Learn more](/) --- # Launch n8n with > Launch a new n8n project with add-ons and you will instantly have access to a development environment. No registration required. Launch a new n8n project and you will instantly have access to a development environment. No sign-up required. - n8n - Workflow automation - AI capabilities [GitHub](https://github.com/diploi/component-n8n) ### Something extra? Choose some optional add-ons to launch with n8n PostgreSQL 9 116 \[ ] Redis 1 450 \[ ] MongoDB 1 347 \[ ] MariaDB 1 245 \[ ] MinIO 385 \[ ] Launch n8n Instant launch. No sign-up required. --- Readme # n8n Component for Diploi Start a demo, no card required A generic n8n component ready to be used for automating tasks. This component was kickstarted running `npm install n8n` and it uses **PostgreSQL** by default. Uses the official [node:22-alpine](https://hub.docker.com/_/node/) Docker image and **n8n** ## Operation ### Getting started 1. In the Dashboard, click Create Project + 1. Under Pick Components, choose **n8n** 1. In Pick Add-ons, you can add one or multiple databases to your app 1. Choose Create Repository, which will generate a new GitHub repo 1. Lastly, click Launch Stack Link to guide, explains how to add a custom domain and launch to production ### Development Will run first `apk add --no-cache libc6-compat` and next `npm install` when component is first initialized, after that the image runs `npx n8n` when the deployment is started. ### Production Will build a production ready image. Image runs `apk add --no-cache libc6-compat` to install all necessary dependencies and `npm ci` to install the necessary packages, to then run `npx n8n`to start the deployment #### IMPORTANT - If you want to create your own custom nodes, you can follow n8n’s official documentation ## Links - [Adding n8n to a project](https://docs.diploi.com/building/components/n8n) - [n8n docs](https://docs.n8n.io/) --- ## What is Diploi? Diploi is the single SaaS service for managing, developing and hosting your full application. - ### Consistent - Consistent environments from development to production - Adoptable incrementally - start easy, grow later - ### One-Click - Fast 30 second new developer onboarding - One-click environment setup - Instantly shareable testing environments - ### Zero-Install - Zero-install remote development - Versatile support for any stack pre-build or custom [Learn more](/) --- # Launch Next.js with > Launch a new Next.js project with add-ons and you will instantly have access to a development environment. No registration required. Launch a new Next.js project and you will instantly have access to a development environment. No sign-up required. - TypeScript - React frontend - Next.js API [GitHub](https://github.com/diploi/component-nextjs) ### Something extra? Choose some optional add-ons to launch with Next.js PostgreSQL 9 116 \[ ] Redis 1 450 \[ ] MongoDB 1 347 \[ ] MariaDB 1 245 \[ ] MinIO 385 \[ ] Launch Next.js Instant launch. No sign-up required. --- Readme # Next.js Component for Diploi Launch a trial, no account needed Uses the official [node](https://hub.docker.com/_/node) Docker image. ## Operation ### Getting started 1. In the Dashboard, click **Create Project +** 1. Under **Pick Components**, choose **Next.js** You can add other frameworks from this page if you want to create a monorepo application, eg, Next.js + Bun for backend. 1. In **Pick Add-ons**, select any databases or extra tools you need. 1. Choose **Create Repository** so Diploi generates a new GitHub repo for your project. 1. Click **Launch Stack** Check the guide ### Development Will run `npm install` when component is first initialized, and `npm run dev` when deployment is started. ### Production Will build a production ready image. Image runs `npm install` & `npm build` when being created. Once the image runs, `npm start` is called. ## Links - [Adding Next.js to a project](https://docs.diploi.com/building/components/nextjs) - [Next.js documentation](https://nextjs.org/docs) --- ## What is Diploi? Diploi is the single SaaS service for managing, developing and hosting your full application. - ### Consistent - Consistent environments from development to production - Adoptable incrementally - start easy, grow later - ### One-Click - Fast 30 second new developer onboarding - One-click environment setup - Instantly shareable testing environments - ### Zero-Install - Zero-install remote development - Versatile support for any stack pre-build or custom [Learn more](/) --- # Launch Node.js with > Launch a new Node.js project with add-ons and you will instantly have access to a development environment. No registration required. Launch a new Node.js project and you will instantly have access to a development environment. No sign-up required. - Generic - Node.js - NPM [GitHub](https://github.com/diploi/component-nodejs) ### Something extra? Choose some optional add-ons to launch with Node.js PostgreSQL 9 116 \[ ] Redis 1 450 \[ ] MongoDB 1 347 \[ ] MariaDB 1 245 \[ ] MinIO 385 \[ ] Launch Node.js Instant launch. No sign-up required. --- Readme # Node.js Component for Diploi Start a demo environment (No card or registration needed) A generic Node.js component that can be used to run any Node.js app. Uses the official [node](https://hub.docker.com/_/node) Docker image. ## Operation ### Getting started 1. In the Dashboard, click **Create Project +** 1. Under **Pick Components**, choose **Node.js** 1. In **Pick Add-ons**, you can add one or multiple databases to your app 1. Choose **Create Repository**, which will generate a new GitHub repo 1. Lastly, click **Launch Stack** Link to guide (includes additional information) ### Development Will run `npm install` when component is first initialized, and `npm run dev` when deployment is started. ### Production Will build a production ready image. Image runs `npm install` & `npm build` when being created. Once the image runs, `npm start` is called. ### Notes - If you are using packages that use native libraries (like `node-canvas` e.g.), it is a good idea to switch the `Dockerfile` and `Dockerfile.dev` to use `node:XX` instead of `node:XX-slim`. You can also add any missing libraries with `RUN apt update && apt install -y ` in the dockerfiles. ## Links - [Adding Node.js to a project](https://docs.diploi.com/building/components/nodejs) - [Node official page](https://nodejs.org/en) --- ## What is Diploi? Diploi is the single SaaS service for managing, developing and hosting your full application. - ### Consistent - Consistent environments from development to production - Adoptable incrementally - start easy, grow later - ### One-Click - Fast 30 second new developer onboarding - One-click environment setup - Instantly shareable testing environments - ### Zero-Install - Zero-install remote development - Versatile support for any stack pre-build or custom [Learn more](/) --- # Launch Nue with > Launch a new Nue project with add-ons and you will instantly have access to a development environment. No registration required. Launch a new Nue project and you will instantly have access to a development environment. No sign-up required. - Nue - Bun - Static prod server [GitHub](https://github.com/diploi/component-nue) ### Something extra? Choose some optional add-ons to launch with Nue PostgreSQL 9 116 \[ ] Redis 1 450 \[ ] MongoDB 1 347 \[ ] MariaDB 1 245 \[ ] MinIO 385 \[ ] Launch Nue Instant launch. No sign-up required. --- Readme # Nue Component for Diploi Start a quick demo, no account needed Uses the official [oven/bun](https://hub.docker.com/r/oven/bun) Docker image for development,\ and an optimised [nginx](https://hub.docker.com/_/nginx) image for production. ## Operation ### Getting started 1. **Sign up** for a free Diploi account at 1. In your Dashboard, click **Create Project +**. 1. Under **Pick Components**, choose **Nue.js**. You can also add databases or other frameworks, to your Nue.js stack here. 1. In **Pick Add‑ons**, select any services your app needs (e.g., PostgreSQL, Redis, or MongoDB). 1. Choose **Create Repository** to start from a fresh GitHub repo. 1. Click **Launch Stack**. For more information, check ### Development Will run `bun install` when component is first initialized, and `bun dev` when deployment is started. ### Production Will build a production ready image. Image runs `bun install` & `bun run build` when being created. ## Links - [Adding Nue.js to a project](https://docs.diploi.com/building/components/nue) - [Nue documentation](https://nuejs.org/docs/) - [Bun documentation](https://bun.sh/docs) --- ## What is Diploi? Diploi is the single SaaS service for managing, developing and hosting your full application. - ### Consistent - Consistent environments from development to production - Adoptable incrementally - start easy, grow later - ### One-Click - Fast 30 second new developer onboarding - One-click environment setup - Instantly shareable testing environments - ### Zero-Install - Zero-install remote development - Versatile support for any stack pre-build or custom [Learn more](/) --- # Launch React + Vite with > Launch a new React + Vite project with add-ons and you will instantly have access to a development environment. No registration required. Launch a new React + Vite project and you will instantly have access to a development environment. No sign-up required. - TypeScript - Vite dev server - Static prod server [GitHub](https://github.com/diploi/component-react-vite) ### Something extra? Choose some optional add-ons to launch with React + Vite PostgreSQL 9 116 \[ ] Redis 1 450 \[ ] MongoDB 1 347 \[ ] MariaDB 1 245 \[ ] MinIO 385 \[ ] Launch React + Vite Instant launch. No sign-up required. --- Readme # React + Vite Component for Diploi Want to start a quick demo? Use this link No account required This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules. ## Operation ### Getting started 1. In the Dashboard, click **Create Project +** 1. Under **Pick Components**, choose **React + Vite**. Here you can also add a backend framework to create a monorepo app, eg, React+Vite for frontend and Hono for backend 1. In **Pick Add-ons**, you can add one or multiple databases to your app 1. Choose **Create Repository** to generate a new GitHub repo 1. Finally, click **Launch Stack** For more details, check ### Development Will run `npm install` when component is first initialized, and `npm run dev` when deployment is started. ### Production Will build a production ready image. Image runs `npm install` & `npm run build` when being created. The created `/dist` folder will be served as a static site with [nginx](https://nginx.org/). ## Links - [Adding React-Vite to a project](https://docs.diploi.com/building/components/react-vite) - [React documentation](https://react.dev/) - [Vite documentation](https://vite.dev/) - [nginx documentation](https://nginx.org/) --- ## What is Diploi? Diploi is the single SaaS service for managing, developing and hosting your full application. - ### Consistent - Consistent environments from development to production - Adoptable incrementally - start easy, grow later - ### One-Click - Fast 30 second new developer onboarding - One-click environment setup - Instantly shareable testing environments - ### Zero-Install - Zero-install remote development - Versatile support for any stack pre-build or custom [Learn more](/) --- # Launch Supabase with > Launch a new Supabase project with add-ons and you will instantly have access to a development environment. No registration required. Launch a new Supabase project and you will instantly have access to a development environment. No sign-up required. - Database & Storage - Authentication - Functions [GitHub](https://github.com/diploi/component-supabase) ### Something extra? Choose some optional add-ons to launch with Supabase PostgreSQL 9 116 \[ ] Redis 1 450 \[ ] MongoDB 1 347 \[ ] MariaDB 1 245 \[ ] MinIO 385 \[ ] Launch Supabase Instant launch. No sign-up required. --- Readme # Supabase Component for Diploi Run [Supabase](https://supabase.com/) on Diploi. Based on the official [supabase/docker](https://github.com/supabase/supabase/tree/master/docker) `docker-compose.yml` file. ## Operation A full Supabase implementation. ### Limitations We know of a few limitations that currently exist with Supabase on Diploi. We are actively working on fixes. - Connection URI’s dislayed on Supabase Studio are wrong, please use the ones on Diploi Console - Logs view on Supabase Studio is empty, please use the logging functionality built-in to Diploi ### Authentication Self-hosted Supabase comes with a simple basic auth implementation by default. Diploi implements custom authentication for the admin panel, making it easier to use. You can authenticate with a single-click from Diploi Console, or use username & password to login. You can find the admin credentials from a deployments “Options” tab in the Diploi Console. ### Development You can develop custom functions with [Deno](https://deno.com/). We will create a `/functions` directory for you with a preconfigured `main` function and an example `hello` function. ## Links - [Adding Supabase to a project](https://docs.diploi.com/building/components/supabase) - [Supabase documentation](https://supabase.com/docs) - [Self-Hosting Supabase with Docker](https://supabase.com/docs/guides/self-hosting/docker) - [Generate Supabase API keys](https://supabase.com/docs/guides/self-hosting/docker#generate-api-keys) --- ## What is Diploi? Diploi is the single SaaS service for managing, developing and hosting your full application. - ### Consistent - Consistent environments from development to production - Adoptable incrementally - start easy, grow later - ### One-Click - Fast 30 second new developer onboarding - One-click environment setup - Instantly shareable testing environments - ### Zero-Install - Zero-install remote development - Versatile support for any stack pre-build or custom [Learn more](/) --- # Launch SvelteKit with > Launch a new SvelteKit project with add-ons and you will instantly have access to a development environment. No registration required. Launch a new SvelteKit project and you will instantly have access to a development environment. No sign-up required. - Svelte - TypeScript - Node.js adapter [GitHub](https://github.com/diploi/component-sveltekit) ### Something extra? Choose some optional add-ons to launch with SvelteKit PostgreSQL 9 116 \[ ] Redis 1 450 \[ ] MongoDB 1 347 \[ ] MariaDB 1 245 \[ ] MinIO 385 \[ ] Launch SvelteKit Instant launch. No sign-up required. --- Readme # SvelteKit Component for Diploi Launch a demo for free Uses the official [node](https://hub.docker.com/_/node) Docker image. Has the [@sveltejs/adapter-node](https://svelte.dev/docs/kit/adapter-node) adapter preconfigured. ## Operation ### Getting started - Create an account on Diploi, it’s free - Once you are in the Dashboard, click on “Create Project +” - Now you need to select the stack for your app. In the “Pick Components” section, select **SvelteKit**. You can add other frameworks to work along with your SvelteKit app. This also applies to the “Pick Add-ons” section, where you can choose the database for your app. - Next, you need to choose “Create Repository” so your new app will start with a fresh repository. - Finally, click “Launch Stack”. Check the full guide ### Development Will run `npm install` when component is first initialized, and `npm run dev` when deployment is started. ### Production Will build a production ready image. Image runs `npm install` & `npm build` when being created. Once the image runs, `npm start` is called. ## Links - [Adding SvelteKit to a project](https://docs.diploi.com/building/components/sveltekit) - [SvelteKit docs](https://svelte.dev/tutorial/kit/introducing-sveltekit) --- ## What is Diploi? Diploi is the single SaaS service for managing, developing and hosting your full application. - ### Consistent - Consistent environments from development to production - Adoptable incrementally - start easy, grow later - ### One-Click - Fast 30 second new developer onboarding - One-click environment setup - Instantly shareable testing environments - ### Zero-Install - Zero-install remote development - Versatile support for any stack pre-build or custom [Learn more](/) --- # Deploy Without DevOps, Code In Your Browser > Create and host applications faster by skipping all server config work. Hey developer 👋 You focus on your app, we handle the config [Launch Trial](#StackBuilder) 1 ## Pick Your Stack Choose from a constantly growing list of technologies to build your ideal stack. We’ll take care of configuring your monorepo. [New](/lovable) [Import from Lovable Go to import page](/lovable) ### Components Base blocks of your Stack. Include editable code. New n8n 516 \[ ] New Laravel 351 \[ ] New FastAPI 335 \[ ] New Flask 291 \[ ] New Deno 274 \[ ] New Supabase 273 \[ ] Next.js 7 841 \[ ] Node.js 3 029 \[ ] Bun 2 840 \[ ] React + Vite 1 961 \[ ] Astro 989 \[ ] SvelteKit 818 \[ ] Nue 780 \[ ] Ghost 530 \[ ] Hono 451 \[ ] Beta Django 565 \[ ] ### Add-ons Complementary services. Configurable with config. PostgreSQL 9 116 \[ ] Redis 1 450 \[ ] MongoDB 1 347 \[ ] MariaDB 1 245 \[ ] MinIO 385 \[ ] diploi.yaml ``` ``` Launch Stack Instant launch. No sign-up required. --- 2 ## Develop Your App Zero-install development environments with a single click. Edit your code directly with our powerful Browser IDE, or connect remotely with your favorite IDE. ### Effortless Development Develop remotely with Diploi using our fast browser IDE, or connect your own over SSH. - Zero-install Browser IDE ........................................... - Local VS Code remote ........................................... - SSH connection ........................................... ### Zero-Install Environments Spin up dev environments instantly, no local setup required. ### Real-Time Logging Quickly view live logs right from your browser. ### GitHub Integration Automatic Git integration with CI/CD setup. Just push it. ### Infrastructure as Code Consistent, predictable environments. Your entire infrastructure configuration will be stored in a single YAML file. ### Custom Components Add custom components to your monorepo for complete control. Kubernetes Docker ### Developer FAQ Quick answers to common developer questions. #### What is Diploi? \[ ] Diploi is a platform that combines cloud development environments and app hosting in a single place, and is meant to be an all-in-one solution where developers can scaffold applications from zero, start developing applications without a local setup using cloud development environments, which do not require any configuration work, and deploy staging and production environments instantly. All applications launched and hosted on Diploi come with a CI/CD pipeline setup by default, automatic SSL certificates, and zero-config cloud development environments. #### Where is my code stored, and how does Git integration work? \[ ] Your code lives in your own GitHub repository. Diploi configures a GitHub Action that triggers a CI/CD workflow that updates your staging and production environments, and is triggered when new updates are pushed to the repository linked to a project hosted in Diploi. #### Is there a limit to how many components or add-ons a project can have in Diploi? \[ ] There is no limit, so you can have all supported frameworks and databases supported by Diploi, the only limitation is the computing power required by a deployment to handle a large stack of components and add-ons. #### Is Diploi a VPS provider? \[ ] No, Diploi is a fully managed development and deployment platform. You cannot choose the OS where your application is deployed, and you do not have configuration access to the server's settings. #### Do I get SSH access to the servers where my project is hosted in Diploi? \[ ] Yes, Diploi uses Kubernetes to host your application's cloud development environment, components, and add-ons as individual pods, which you can access via SSH. #### Can I share my application with others for testing? \[ ] Yes, each environment has a unique URL you can share, so others can access and test your app instantly. #### How do I monitor logs or production status? \[ ] Diploi provides real-time logging for each component and add-on that is part of your application. Additionally, from the deployment's dashboard, you have access to graphs showing the resource usage of your app's cluster and its current health status. Additionally, all development deployments on Diploi come with a Diploi CLI, which gives you access to logs in real-time and can be used for programmatic log data tracking #### What if I want to move off Diploi later? \[ ] You can move your project out of Diploi at any point. All Diploi projects can be run on any VPS or managed hosting service, either by running each component and add-on as you usually would do via terminal commands (eg. npm run start), or by using the Dockerfiles that Diploi generates for your app's components. #### Is there a free trial or credits? \[ ] When you sign up with GitHub, you receive €50 in free credits valid for 14 days. These credits let you explore Diploi fully without a credit card. After the trial, you only pay for the time that your application is online and the storage utilized. There are no additional costs or fees for extra services. #### What is the Stack Builder in Diploi? \[ ] Stack Builder is a tool for scaffolding new apps. It can generate boilerplate code and project structure for common stacks. For example, you can pick frameworks and databases, and the Stack Builder will create a ready-to-launch application template. This jumpstarts new projects so you can begin coding immediately. --- 3 ## Publish Your App We take care of the full lifecycle of your app. You can spin up any kind of environment with a single click. ### Test Environments Create staging environments to test your application with a single click. ### Share With Link Share access to environments with a web link and invite anyone to test. ### CI/CD Automatically configured GitHub actions for easy CI/CD pipelines. ### Push to Deploy Automatically update environments with a push, including infrastructure. ### Monitor Production Single-click access to logs. Easy to read status trees for environment services. --- ## Benefits of Diploi These are real-life statistics from a web development company. Can you afford to ignore the benefits and savings from Diploi? ### Consistent - Consistent environments from development to production - Straightforward yet powerful user experience - Adoptable incrementally - start easy, grow later ### One-Click - Fast 30 second new developer onboarding - One-click environment setup - Instantly shareable testing environments ### Zero-Install - Zero-install remote development - Versatile support for any stack pre-build or custom ### This means, that on average, Diploi saves300hfor every developer, every year. ### [Diploi for Developers](/features/dev) [Zero-install cloud development](/features/dev) ### [Diploi for Teams](/features/teams) [Ship faster with zero-config](/features/teams) ### [Diploi for DevOps](/features/devops) [GitOps & push to deploy](/features/devops) ### [Diploi for Vibes & AI](/features/ai) [From vibes to prod with zero-config](/features/ai) ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) ## Contact Us If you're considering our Pro or Enterprise tiers, feel free to reach out to us directly. We're here to answer your questions and assist with upgrading your account. [Book a Demo](https://calendly.com/hello-diploi/30min) --- # Vibes & AI > Diploi allows you to integrates AI in your remote development environments instantly. Work in VS Code or Cursor AI with no local setup. ### VS Code Officially supported - Copilot, agent mode - Full extensions support --- ### Cursor Officially supported - Agent mode, autocomplete, chat - Full extensions support --- ### SSH Officially supported - Full control over your environment - Any Debian ARM package supported --- [Remote development with Diploi ](/dev)[Exploring 7 Lesser Known AI Coding Extensions for VS Code ](/blog/exploring-7-lesser-known-ai-coding-extensions)[7 Remote Development Platforms in 2025, to Code without a Local Setup ](/blog/remote_development_platforms)[Remote Development Environments with Cursor?](/blog/remote-development-with-cursor-4okl) 1. Could you create a new Node.js microservice for proxying image requests? 1. Certainly! Adding a new Node.js component to `diploi.yaml`... [Our IaC implementation](https://dev.to/diploi/how-we-solved-infrastructure-as-code-2ldn) diploi.yaml ``` diploiVersion: "v1.0" components: - name: "Next.js" identifier: "next" package: "https://github.com/diploi/component-nextjs#main" - name: "Node.js" identifier: "node" package: "https://github.com/diploi/component-nodejs#main" ``` [New](/lovable) [Import from Lovable Go to import page](/lovable) ### Components Base blocks of your Stack. Include editable code. New n8n 516 \[ ] New Laravel 351 \[ ] New FastAPI 335 \[ ] New Flask 291 \[ ] New Deno 274 \[ ] New Supabase 273 \[ ] Next.js 7 841 \[ ] Node.js 3 029 \[ ] Bun 2 840 \[ ] React + Vite 1 961 \[ ] Astro 989 \[ ] SvelteKit 818 \[ ] Nue 780 \[ ] Ghost 530 \[ ] Hono 451 \[ ] Beta Django 565 \[ ] ### Add-ons Complementary services. Configurable with config. PostgreSQL 9 116 \[ ] Redis 1 450 \[ ] MongoDB 1 347 \[ ] MariaDB 1 245 \[ ] MinIO 385 \[ ] diploi.yaml ``` ``` Launch Stack Instant launch. No sign-up required. ## FAQ Answers to common questions about how AI can be used on Diploi #### What does "AI" mean in Diploi's context? \[ ] Diploi supports AI tools throughout the development lifecycle while keeping you in control. Since each deployment is independent, you can use Diploi as a way to provision sandboxed environments to run AI-generated code. #### Am I locked into Diploi's tools for AI? \[ ] No, you can use any editor or tool over SSH (including your existing tools) and optionally use Diploi’s AI features. It’s fully compatible with the workflows you already know. #### Where does my code live, and can I still use my own repos? \[ ] Your code stays within your deployments, which can be synced with your own Git repository. You can always use your own Git repo, as long as it uses GitHub. We also support other Git providers, but it requires additional configuration, so please reach out to our team if you would like to use Diploi with a different Git solution like GitLab or GitBucket. #### Are Diploi's components and add-ons open source? \[ ] Yes, all of Diploi’s supported stack components and add-ons are open source and available on GitHub. You can inspect them and make suggestions for changes via GitHub issues or by making your own pull request. You can find them in our GitHub repository https\://github.com/orgs/diploi/repositories #### Which code editors have special AI support? \[ ] Officially supported editors include VS Code and Cursor. In VS Code, you can use GitHub Copilot and agent mode, and in Cursor, you get autocomplete, chat, and agent features. You can also use any other IDE that supports remote SSH connection to connect to your development environments. ### [Diploi for Developers](/features/dev) [Zero-install cloud development](/features/dev) ### [Diploi for Teams](/features/teams) [Ship faster with zero-config](/features/teams) ### [Diploi for DevOps](/features/devops) [GitOps & push to deploy](/features/devops) ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) ## Contact Us If you're considering our Pro or Enterprise tiers, feel free to reach out to us directly. We're here to answer your questions and assist with upgrading your account. [Book a Demo](https://calendly.com/hello-diploi/30min) --- # Developers > Diploi is the all-in-one remote development platform — one platform from code to deployment. ### Development - Powerful VM for development - Cloud IDE or any custom IDE - Stack Builder for scaffolding apps git push ### Preview - Share with a link - Tail logs, login with SSH - Automatic Git, CI/CD, SSL, e.g. Apply Changes ### Production - Consistent with development - Optimized deployments - One-click setup ### Cloud IDE - Code in the browser - Full extensions support --- ### Cursor Officially supported - Agent mode, autocomplete, chat - Full extensions support --- ### VS Code Officially supported - Copilot, agent mode - Full extensions support --- [Remote development with Diploi ](/dev)[Exploring 7 Lesser Known AI Coding Extensions for VS Code ](/blog/exploring-7-lesser-known-ai-coding-extensions)[7 Remote Development Platforms in 2025, to Code without a Local Setup ](/blog/remote_development_platforms)[Remote Development Environments with Cursor?](/blog/remote-development-with-cursor-4okl) * ### Individual Environments Your own environment. Your own IDE. Connect to others whenever you need to. - Zero-install remote development - One-click environment setup - 30 second developer onboarding * --- ### GitHub Workflow Git that works the way you do. Pull requests, Actions, or plain CLI. - GitHub integration - Automatic Git, CI/CD, SSL - Infrastructure as code * --- ### Easy Previews Want to demo a feature? Share the link. You can spin up endless environments. - Shareable environment URLs - One-click environment cloning - Real-time logging ### Components Base blocks of your Stack. Include editable code. New n8n 516 \[ ] New Laravel 351 \[ ] New FastAPI 335 \[ ] New Flask 291 \[ ] New Deno 274 \[ ] New Supabase 273 \[ ] Next.js 7 841 \[ ] Node.js 3 029 \[ ] Bun 2 840 \[ ] React + Vite 1 961 \[ ] Astro 989 \[ ] SvelteKit 818 \[ ] Nue 780 \[ ] Ghost 530 \[ ] Hono 451 \[ ] Beta Django 565 \[ ] ### Add-ons Complementary services. Configurable with config. PostgreSQL 9 116 \[ ] Redis 1 450 \[ ] MongoDB 1 347 \[ ] MariaDB 1 245 \[ ] MinIO 385 \[ ] diploi.yaml ``` ``` Launch Stack Instant launch. No sign-up required. - ### [Hosting a Ghost blog in seconds on Diploi, with support for custom development](/blog/hosting_a_ghost_blog) [Learn how to create blogs and websites with Ghost using Diploi](/blog/hosting_a_ghost_blog) [- Guide- August 27, 2025](/blog/hosting_a_ghost_blog) - ### [Create Astro apps quickly, from Development to Production on Diploi](/blog/hosting_astro_apps) [Bring the versatility of platforms like Heroku to your Astro development workflow](/blog/hosting_astro_apps) [- Guide- August 26, 2025](/blog/hosting_astro_apps) - ### [Launching SvelteKit apps, from Development to Production using Diploi](/blog/hosting_svelte_apps) [With the convenience of Vercel and the flexibility of Replit, all in a single platform, to create SvelteKit-powered apps super fast](/blog/hosting_svelte_apps) [- Guide- August 18, 2025](/blog/hosting_svelte_apps) - ### [7 Remote Development Platforms in 2025, to Code without a Local Setup](/blog/remote_development_platforms) [We discuss 7 remote development platforms that you can use in 2025 to code, run, and test applications in the cloud without the need for a local setup](/blog/remote_development_platforms) [- Blog- June 10, 2025](/blog/remote_development_platforms) - ### [Remote Development Environments with Cursor?](/blog/remote-development-with-cursor-4okl) [Now you can connect to your remote development environments on Diploi using Cursor ...](/blog/remote-development-with-cursor-4okl) [- Blog- May 6, 2025- Dev.to](/blog/remote-development-with-cursor-4okl) ## FAQ Common questions about Diploi's features for developers #### Is Diploi for Developers or Vibecoders? \[ ] Diploi is built with developers in mind, as a way to simplify how apps with diverse stacks can be built and hosted without requiring complicated setups to allow context switching. That said, it is also designed to help casual users who are interested in Vibecoding as a way to build web applications, but it requires at least some familiarity with concepts like SSH and Git workflows to take advantage of all the features of Diploi. #### Which IDEs are supported on Diploi? \[ ] You have multiple options. Diploi has a built-in browser-based IDE, and you can also connect any IDE with support for SSH and devcontainers. By default, Diploi provides native support for VS Code and Cursor, but you can also connect to a Diploi cloud development environment by configuring a remote connection using SSH from Zed, Windsurf, and JetBrains IDEs. #### How do I deploy my application on Diploi? \[ ] All applications kick-started in Diploi are deployed online by default and do not require any special configuration. If you have an existing project on GitHub, you can import it, and Diploi will generate the configuration necessary to host it online, but in some cases, this process might require some changes to work properly. If you are having issues, please reach out via email at hello\@diploi.com or message us on Discord. #### How do teams collaborate on Diploi? \[ ] On Diploi, each project can have independent development deployments for each developer in a team. You can share a link to an environment and even access a teammate’s environment directly. Environments can be cloned and shared for previewing purposes. Onboarding a new developer is fast, requiring about 30 seconds to get them up and running, since there's no local configuration required or limitations based on the developer's OS of preference. ### [Diploi for Teams](/features/teams) [Ship faster with zero-config](/features/teams) ### [Diploi for DevOps](/features/devops) [GitOps & push to deploy](/features/devops) ### [Diploi for Vibes & AI](/features/ai) [From vibes to prod with zero-config](/features/ai) ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) ## Contact Us If you're considering our Pro or Enterprise tiers, feel free to reach out to us directly. We're here to answer your questions and assist with upgrading your account. [Book a Demo](https://calendly.com/hello-diploi/30min) --- # DevOps > Infrastructure that configures itself. Diploi gives you development, preview, and production environments with a single YAML file. ### Development - Powerful VM for development - Cloud IDE or any custom IDE - Stack Builder for scaffolding apps git push ### Preview - Share with a link - Tail logs, login with SSH - Automatic Git, CI/CD, SSL, e.g. Apply Changes ### Production - Consistent with development - Optimized deployments - One-click setup * ### Component-Based Model Component configs (HELM, Docker, and more) live in dedicated GitHub repos, making them easy to share, version, and maintain. * --- ### Inline Components Coming soon You can inline components locally for full control. Create custom components for your project, or inline an existing component to customize everything. [Our IaC implementation](https://dev.to/diploi/how-we-solved-infrastructure-as-code-2ldn) diploi.yaml ``` diploiVersion: "v1.0" components: - name: "Next.js" identifier: "next" package: "https://github.com/diploi/component-nextjs#main" - name: "Node.js" identifier: "node" package: "https://github.com/diploi/component-nodejs#main" ``` * ### Incremental Adoption Start small by running parts of your stack on Diploi while keeping your current production setup. Even our dev environments alone make a big difference to productivity. Your cloud services Diploi can run your deployments in the same AWS VPC as your existing infrastucture. [Book a Call](https://calendly.com/hello-diploi/30min) Private Cloud is available for Enterprise customers. Book a call and let's find the best solution for you! * --- ### Maximum Efficiency Move your stack to Diploi for consistent environments from dev to prod. Set up entire environments with a single click, onboard devs in 30-seconds. Diploi supports even the most complex setups. If it can be containerized, it can run on Diploi. Need help migrating? We provide developer resources and consultation to get your setup onto Diploi smoothly. ******************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************** - ### [Deploying Flask Apps the Easy Way](/blog/hosting_flask_apps) [Use Diploi to run and iterate on Flask without touching servers](/blog/hosting_flask_apps) [- Guide- September 22, 2025](/blog/hosting_flask_apps) - ### [Deploying Deno Applications in Easy Mode](/blog/hosting_deno_apps) [How to use Diploi to host and develop Deno-powered apps without configuring servers](/blog/hosting_deno_apps) [- Guide- September 22, 2025](/blog/hosting_deno_apps) - ### [Launching a new Node app? How to do it, without configuring a server](/blog/hosting_node_apps) [Build your next Node.js app with Diploi and have it live right away](/blog/hosting_node_apps) [- Guide- August 21, 2025](/blog/hosting_node_apps) - ### [Ship new React apps using Diploi and skip the server config](/blog/hosting_react_apps) [Create your next React app using Diploi to skip any DevOps work and focus only on the code](/blog/hosting_react_apps) [- Guide- August 19, 2025](/blog/hosting_react_apps) - ### [Skip the YAML and Server Configs: 7 Easy Deployment Platforms You Haven’t Tried](/blog/deployment-platforms) [We created a list of deployment platforms (us included) that you should check out to make your development workflow faster](/blog/deployment-platforms) [- Blog- May 27, 2025](/blog/deployment-platforms) ## FAQ Frequently asked questions about Diploi within the context of DevOps #### How is infrastructure configured on Diploi? \[ ] Diploi uses an Infrastructure-as-Code model where your entire stack is defined in a single YAML file (diploi.yaml). In this file, you list components, add-ons, and settings, which Diploi uses to automatically create development, staging, and production environments. #### What is "GitOps" or "push to deploy" on Diploi? \[ ] GitOps on Diploi means Git is the single source of truth. As for "push to deploy", we mean that when you want to deploy an update, you simply push your code (\`git push\`), and Diploi automatically builds and deploys it across environments. #### How are CI/CD pipelines automatically handled? \[ ] Diploi pre-configures new and imported GitHub projects, with a GitHub Action that is generated based on the contents of the \`diploi.yaml\` file, which adds a CI/CD pipeline that updates development and staging/production deployments that belong to the project. #### Can I preview changes before production? \[ ] Yes, Diploi provides live endpoints for all deployments, which allows you to preview your applications. #### Can we integrate Diploi with our current cloud setup? \[ ] Yes, Diploi can be integrated with your existing infrastructure. Reach out to our team for more information. #### Is Diploi suitable for large or complex stacks? \[ ] Yes, Diploi can run any application, but it might require some additional configuration. We provide migration services to run your existing projects on Diploi. ### [Diploi for Developers](/features/dev) [Zero-install cloud development](/features/dev) ### [Diploi for Teams](/features/teams) [Ship faster with zero-config](/features/teams) ### [Diploi for Vibes & AI](/features/ai) [From vibes to prod with zero-config](/features/ai) ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) ## Contact Us If you're considering our Pro or Enterprise tiers, feel free to reach out to us directly. We're here to answer your questions and assist with upgrading your account. [Book a Demo](https://calendly.com/hello-diploi/30min) --- # Teams > Diploi gives your team the workflow to focus on code and ship faster. Onboarding new developers now takes seconds, not days. * ### Incremental Adoption Start small by running parts of your stack on Diploi while keeping your current production setup. Even our dev environments alone make a big difference to productivity. Your cloud services Diploi can run your deployments in the same AWS VPC as your existing infrastucture. [Book a Call](https://calendly.com/hello-diploi/30min) Private Cloud is available for Enterprise customers. Book a call and let's find the best solution for you! * --- ### Maximum Efficiency Move your stack to Diploi for consistent environments from dev to prod. Set up entire environments with a single click, onboard devs in 30-seconds. Diploi supports even the most complex setups. If it can be containerized, it can run on Diploi. Need help migrating? We provide developer resources and consultation to get your setup onto Diploi smoothly. ### Development - Powerful VM for development - Cloud IDE or any custom IDE - Stack Builder for scaffolding apps git push ### Preview - Share with a link - Tail logs, login with SSH - Automatic Git, CI/CD, SSL, e.g. Apply Changes ### Production - Consistent with development - Optimized deployments - One-click setup * ### Nothing Installed Locally Local devices hold no source code or infrastructure access, leaving malware and ransomware with nothing to target. - Zero-install remote development - Cloud IDE * --- ### Complete Control Centralize and manage access to your entire infrastructure from a single, unified control panel. - Central access control - Central authentication * --- ### Isolated Environments Developers run in fully isolated VMs. No environment shares data, processes, or resources. - Individual VMs - Infrastructure as code - ### [How to create Laravel apps that are ready for Production using Diploi](/blog/hosting_laravel_apps) [In this tutorial guide we go over the process of creating and hosting an application using Laravel in Diploi](/blog/hosting_laravel_apps) [- Guide- September 22, 2025](/blog/hosting_laravel_apps) - ### [Create Astro apps quickly, from Development to Production on Diploi](/blog/hosting_astro_apps) [Bring the versatility of platforms like Heroku to your Astro development workflow](/blog/hosting_astro_apps) [- Guide- August 26, 2025](/blog/hosting_astro_apps) - ### [How to create Hono apps that are ready for Production using Diploi](/blog/hosting_hono_apps) [Make your Hono development as seamless as deploying on Heroku](/blog/hosting_hono_apps) [- Guide- August 23, 2025](/blog/hosting_hono_apps) - ### [Creating ready-for-Production Next.js apps using Diploi](/blog/hosting_nextjs_apps) [Launching Next.js faster than using Vercel and with support for monorepo apps](/blog/hosting_nextjs_apps) [- Guide- August 22, 2025](/blog/hosting_nextjs_apps) - ### [Launching SvelteKit apps, from Development to Production using Diploi](/blog/hosting_svelte_apps) [With the convenience of Vercel and the flexibility of Replit, all in a single platform, to create SvelteKit-powered apps super fast](/blog/hosting_svelte_apps) [- Guide- August 18, 2025](/blog/hosting_svelte_apps) ## FAQ Answers to common questions about Diploi's features for teams #### Can Diploi integrate with our existing infrastructure? \[ ] Yes, for Enterprise clients, we provide support for on-premise and bring-your-own-cloud setups, so you can get the user experience that Diploi offers, while still running your current cloud. #### How does Diploi improve team efficiency? \[ ] By simplifying context switching, developers can move between projects using different configurations at ease, without requiring any time to customize their local environment, which also removes all "works on my machine" issues. Diploi also reduces handoff time, since projects can be transferred to clients without requiring any management for custom infrastructure configuration, helping teams minimize the amount of time spent to deliver a project. #### What security measures does Diploi provide for teams? \[ ] Diploi keeps projects secure by default, since developers do not need to copy source code or credentials on their local machines, minimizing the exposure to data breaches. Access is centrally controlled (with unified auth and permissions), and each developer’s VM is isolated from others. #### How are access and permissions managed? \[ ] Diploi provides central access control, so team leads can manage team permissions and authentication for all environments from a single dashboard. This means you have full visibility and control over who can access each project or environment. #### How isolated are development environments? \[ ] Each developer in a team can get an individual cloud development environment. No environment shares processes, file systems, or credentials with another. ### [Diploi for Developers](/features/dev) [Zero-install cloud development](/features/dev) ### [Diploi for DevOps](/features/devops) [GitOps & push to deploy](/features/devops) ### [Diploi for Vibes & AI](/features/ai) [From vibes to prod with zero-config](/features/ai) ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) ## Contact Us If you're considering our Pro or Enterprise tiers, feel free to reach out to us directly. We're here to answer your questions and assist with upgrading your account. [Book a Demo](https://calendly.com/hello-diploi/30min) --- # Jobs > Check our available job openings. ## Join Us ### Who We Are Diploi is redefining cloud development with a **simple**, **scalable**, and **powerful** PaaS solution. Our goal is to provide a Developer Experience that looks and feels just magical.\ \ We're still early on, but with recent funding and and a mindset to innovate, we aim to grow fast! Now, we're looking for more passionate people to join us. ### Who We're Looking For We are hiring Software Developers who obsess with - Developer Experience - Artificial Intelligence - Scalability & Performance - Working on hard tasks and having a good time Experience with social media and online publishing is seen as a bonus.\ \ You don't need to check every box, but if you're **curious, driven and love solving hard problems**, we'd love to hear from you! ### Open Positions * --- [### Full-Stack / AI EngineerWork across frontend & backend to enhance our solution. Enhancing our the AI capabilites of Diploi will be a big part of your work.](/jobs/ai) --- ### Backend / DevOps Engineer Focus on performance, reliability, and cloud automation. --- **Not seeing your role or you might tick several boxes?** Reach out anyway, because we're looking for exceptional talent! ## How to apply Email us at with - Your resume / LinkedIn / GitHub - A short intro about why you're interested - Any projects or code you're proud of Come and create magic with us! ## FAQ Frequently asked questions about our hiring practices #### What is Diploi's mission? \[ ] Diploi is a company building a simple, scalable PaaS for cloud development. Our mission is to deliver a developer experience that looks and feels magical. We aim to redefine how devs code by removing the boring work involved in building web applications. #### What kind of people is Diploi looking to hire? \[ ] At Diploi we hire people who are passionate about developer experience, scalability, and tackling hard problems. We value curiosity, drive, and love for challenges. #### Do I need to meet every listed qualification? \[ ] No, you don’t need to check every box. We are more interested in curious and driven people than in your accolades. If you’re eager and a quick learner, we want to hear from you, even if you don’t match every requirement. #### What should I include in my application? \[ ] Along with your resume or CV, we ask for a short intro explaining your interest and any relevant projects or code you’ve worked on. Showing real examples of your work (eg. GitHub repos, demos) is especially helpful. --- # Jobs > Learn about our AI job role. ## Full-stack developer with interest in AI ### TL;DR We are looking for a full-stack developer with a keen interest in working with AI solutions.\ If you think you are able to develop features that change the future of software engineering this position is for you. ### Who We Are Diploi is redefining cloud development with a **simple**, **scalable**, and **powerful** PaaS solution. Our goal is to provide a Developer Experience that looks and feels just magical.\ \ We are still very early on so joining now will enable you to make a real impact on the product as well as being one of the first employees. ### Who We're Looking For We are hiring Software Developers who obsess with - Developer Experience - Artificial Intelligence - Scalability & Performance - Working on hard tasks and having a good time You don't need to check every box, but if you're curious, driven and love solving hard problems, we'd love to hear from you!\ \ Our offices are in Helsinki, Finland and we work on-site once per week. We would prefer if you can do that also. **Our Tech Stack**\ \ Frontend: React for user interfaces\ Backend: Typescript, PostgreSQL, Kubernetes\ Cloud: Cloudflare, AWS, Terraform ## How to apply Email us at with - Your resume / LinkedIn / GitHub - A short intro about why you're interested - Any projects or code you're proud of Come and create magic with us! --- # Launch Week > Launch Week is here! We're rolling out new features and components to make your development flow smoother, faster, and more magical. 1. ### Monday Day one brings two big additions: [Laravel](/component/laravel) and [Deno](/component/deno). Laravel introduces **official PHP support on Diploi**, while Deno expands our JS/TS roster with powerful package management and fine-grained process permissions. - #### Laravel New The PHP framework for web artisans. Running on FrankenPHP. [Launch Laravel ](/component/laravel)[Read guide](/blog/hosting_laravel_apps) - #### Deno New The next-generation JavaScript runtime. Now available with a single-click. [Launch Deno ](/component/deno)[Read guide](/blog/hosting_deno_apps) 1. ### Tuesday It's Python's turn! Day two brings **two of the most popular Python web frameworks**, [FastAPI](/component/fastapi) and [Flask](/component/flask), to Diploi. Launch them with a single-click and start building faster than ever. - #### FastAPI New Modern, fast, web framework for building APIs with standard type hints. [Launch FastAPI ](/component/fastapi)[Read guide](/blog/hosting_fastapi_apps) - #### Flask New Lightweight, easy, scalable WSGI web application framework. [Launch Flask ](/component/flask)[Read guide](/blog/hosting_flask_apps) 1. ### Wednesday Day three expands Diploi's advanced toolkit with [n8n](/component/n8n). Build powerful automations, schedule tasks seamlessly, and take advantage of **custom nodes right out of the box**. - #### n8n New Build with the precision of code or the speed of drag-n-drop. n8n gives you more freedom to implement multi-step AI agents and integrate apps than any other tool. [Launch n8n ](/component/n8n)[Read guide](/blog/hosting_n8n) 1. ### Thursday Day four brings our biggest component yet: [Supabase](/component/supabase)! With a full Postgres database, built-in authentication, powerful storage, and edge functions, Supabase makes it effortless to add **a complete backend to your project**. From idea to production, you now have everything you need with zero-setup. - #### Supabase New Start your project with a Postgres database, Authentication, instant APIs, Edge Functions, Realtime subscriptions, Storage, and Vector embeddings. [Launch Supabase ](/component/supabase)[Read guide](/blog/hosting_supabase) 1. ### Friday We're closing Launch Week with something special: **direct imports from Lovable**. [Lovable](https://lovable.dev/) is perfect for vibe-coding, while Diploi gives you the power to take projects further. **Just connect your Lovable project to GitHub, select it in Diploi**, and you're ready to go. You can even keep working across both platforms at the same time. - #### Lovable New Official support for Lovable repositories. When logged into Diploi, create a new project and select "Import Repository" to get started. [Read guide](/blog/importing_from_lovable_and_github) --- * ### No vendor lock-in Use any tool over SSH. Use our AI features, or stick with the editors and workflows you already know. * --- ### Your own repository Diploi integrates with your Git repository, so you can work with any Git-compatible tools, even outside the platform. * --- ### Open source components All our stack components are open source and available on [GitHub](https://github.com/diploi). No black boxes, no hidden surprises. --- - Zero-install remote development - GitHub integration - Code in the browser - One-click environment setup - Infrastructure as code - Real-time logging - [Stack Builder](#stack-builder) for scaffolding apps - Automatic Git, CI/CD, SSL - 30 second developer onboarding [Documentation](https://docs.diploi.com/) --- [New](/lovable) [Import from Lovable Go to import page](/lovable) ### Components Base blocks of your Stack. Include editable code. New n8n 516 \[ ] New Laravel 351 \[ ] New FastAPI 335 \[ ] New Flask 291 \[ ] New Deno 274 \[ ] New Supabase 273 \[ ] Next.js 7 841 \[ ] Node.js 3 029 \[ ] Bun 2 840 \[ ] React + Vite 1 961 \[ ] Astro 989 \[ ] SvelteKit 818 \[ ] Nue 780 \[ ] Ghost 530 \[ ] Hono 451 \[ ] Beta Django 565 \[ ] ### Add-ons Complementary services. Configurable with config. PostgreSQL 9 116 \[ ] Redis 1 450 \[ ] MongoDB 1 347 \[ ] MariaDB 1 245 \[ ] MinIO 385 \[ ] diploi.yaml ``` ``` Launch Stack Instant launch. No sign-up required. --- ### [Diploi for Developers](/features/dev) [Zero-install cloud development](/features/dev) ### [Diploi for Teams](/features/teams) [Ship faster with zero-config](/features/teams) ### [Diploi for DevOps](/features/devops) [GitOps & push to deploy](/features/devops) ### [Diploi for Vibes & AI](/features/ai) [From vibes to prod with zero-config](/features/ai) ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) ## Contact Us If you're considering our Pro or Enterprise tiers, feel free to reach out to us directly. We're here to answer your questions and assist with upgrading your account. [Book a Demo](https://calendly.com/hello-diploi/30min) --- # Level Up YourLovable Apps > Extend apps built with Lovable by migrating to Diploi, to use Cursor, add databases or backend services, and deploy staging/production environments with zero DevOps. ### Cursor Officially supported - Agent mode, autocomplete, chat - Full extensions support --- ### VS Code Officially supported - Copilot, agent mode - Full extensions support --- ### SSH Officially supported - Full control over your environment - Any Debian ARM package supported --- [Remote development with Diploi ](/dev)[Exploring 7 Lesser Known AI Coding Extensions for VS Code ](/blog/exploring-7-lesser-known-ai-coding-extensions)[7 Remote Development Platforms in 2025, to Code without a Local Setup ](/blog/remote_development_platforms)[Remote Development Environments with Cursor?](/blog/remote-development-with-cursor-4okl) * ### Individual Environments Your own environment. Your own IDE. Connect to others whenever you need to. - Zero-install remote development - One-click environment setup - 30 second developer onboarding * --- ### GitHub Workflow Git that works the way you do. Pull requests, Actions, or plain CLI. - GitHub integration - Automatic Git, CI/CD, SSL - Infrastructure as code * --- ### Easy Previews Want to demo a feature? Share the link. You can spin up endless environments. - Shareable environment URLs - One-click environment cloning - Real-time logging * Cursor for development * --- Frontend created with Lovable * Self-hosted [Supabase](/component/supabase) as the backend * [n8n](/component/n8n) for AI automation --- * Zed for development * --- Frontend created with Lovable * Custom [Node.js](/component/node) backend * [Ghost](/component/ghost) as a CMS --- * VS Code for development * --- Frontend created with Lovable * An API created with [Laravel](/component/laravel) * PostgreSQL for data storage --- [Supabase on Diploi ](/blog/hosting_supabase)[Hosting n8n on Diploi ](/blog/hosting_n8n)[How to create Laravel apps that are ready for Production using Diploi ](/blog/hosting_laravel_apps)[Hosting a Ghost blog in seconds on Diploi, with support for custom development](/blog/hosting_a_ghost_blog) - ### [Using Cursor with apps built with Lovable, and hosting without Lovable Cloud](/blog/importing_from_lovable) [Import and deploy Lovable AI apps directly from your GitHub account or public repositories and code with Cursor](/blog/importing_from_lovable) [- Guide- October 17, 2025](/blog/importing_from_lovable) - ### [Importing Lovable apps and more from an existing Repository to Diploi](/blog/importing_from_lovable_and_github) [You can now import apps directly from your GitHub account or public repositories, and host them instantly on Diploi](/blog/importing_from_lovable_and_github) [- Guide- September 26, 2025](/blog/importing_from_lovable_and_github) - ### [Supabase on Diploi](/blog/hosting_supabase) [How to get started with Supabase, using Diploi to host a project.](/blog/hosting_supabase) [- Guide- September 25, 2025](/blog/hosting_supabase) - ### [Exploring 7 Lesser Known AI Coding Extensions for VS Code](/blog/exploring-7-lesser-known-ai-coding-extensions) [In this article, we check interesting AI coding alternatives to the popular AI coding tools in the Visual Studio Marketplace](/blog/exploring-7-lesser-known-ai-coding-extensions) [- Blog- September 18, 2025](/blog/exploring-7-lesser-known-ai-coding-extensions) - ### [7 Remote Development Platforms in 2025, to Code without a Local Setup](/blog/remote_development_platforms) [We discuss 7 remote development platforms that you can use in 2025 to code, run, and test applications in the cloud without the need for a local setup](/blog/remote_development_platforms) [- Blog- June 10, 2025](/blog/remote_development_platforms) - ### [Remote Development Environments with Cursor?](/blog/remote-development-with-cursor-4okl) [Now you can connect to your remote development environments on Diploi using Cursor ...](/blog/remote-development-with-cursor-4okl) [- Blog- May 6, 2025- Dev.to](/blog/remote-development-with-cursor-4okl) Ready to Level Up?\ Give Us a Try! -------------- [Import Lovable Project](https://console.diploi.com/import/lovable) ### [Diploi for Developers](/features/dev) [Zero-install cloud development](/features/dev) ### [Diploi for Teams](/features/teams) [Ship faster with zero-config](/features/teams) ### [Diploi for DevOps](/features/devops) [GitOps & push to deploy](/features/devops) ### [Diploi for Vibes & AI](/features/ai) [From vibes to prod with zero-config](/features/ai) ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) ## Contact Us If you're considering our Pro or Enterprise tiers, feel free to reach out to us directly. We're here to answer your questions and assist with upgrading your account. [Book a Demo](https://calendly.com/hello-diploi/30min) --- # Pricing > Usage-based pricing for cloud app hosting. Pay only for what you use, starting at €0.026/hour for a full environment. ## Simple, Predictable Pricing **50€** [Sign Up & Claim](https://console.diploi.com) - Powerful cluster tuned for development - Stack Builder for scaffolding apps - Browser, VS Code, Cursor, and custom IDE support - Automatic Git, CI/CD, SSL, eg. configuration - And more * Always hot, no cold-starts * Consistent with development * Automated optimized deployments * One-click setup * And more Taxes / VAT not included --- - Direct priority support - Migration & integration services - Custom components --- ## Cluster Costs A running Diploi deployment spins up a cluster that runs everything to do with your stack. You will only be charged for the hours your cluster is running. I want to use Diploi for \[ ] Development \[ ] Testing \[ ] Production Assuming a developer uses the environment 7 hours / workday. A test environment needs to run only when needed, we assume 25 % of the time. A production environment will run 24/7. Cluster size | Memory | vCPU | €/hour | €/month S | 4 GB | 2 | 0,026 € M | 8 GB | 2 | 0,048 € L | 16 GB | 4 | 0,089 € XL | 32 GB | 8 | 0,182 € --- Size | €/GB/hour | €/month Storage | 0,00 € | 1,80 € ## FAQ Common questions about Diploi's pricing #### What is the pricing model of Diploi? \[ ] Diploi has a usage-based pricing model, where you only pay for the hours that your deployment is running and the storage used. This applies to development, testing, and production environments alike. #### Can I use Diploi for free? \[ ] Yes, you can use Diploi free for 14 days when you register for first time. There are no upfront fees or credit card requirements. After that you need to add a valid payment method, because Diploi does not offer a free tier. #### How much does a development or production environment cost? \[ ] Costs depend on the cluster size, storage needs, and the amount of time online per deployment. For example, a size M cluster (2 cores, 8gb ram), with 10gb of storage, and used for cloud development for 7 hours per workday, costs €9 per month. A smaller size S cluster (2 cores, 4gb ram), with 10gb of storage, meant for production and running full-time (24/7) would cost €21 per month. #### Are there enterprise plans? \[ ] Yes, we offer an Enterprise tier with tailored pricing and custom services. Enterprise customers get priority support, migration services, integration assistance, and the ability to add custom components to the platform. If you are interested, message us at hello\@diploi.com or book a call with our team here https\://calendly.com/hello-diploi/30min. #### Are taxes or VAT included in these prices? \[ ] No, listed prices do not include taxes or VAT. Taxes will be added according to your location. --- ## Get Started Sign up using your GitHub account and receive 50 € in free credits (valid for 14 days) to explore and experiment with. Development is about to get **magical**. [Sign Up](https://console.diploi.com/sign-up) ## Contact Us If you're considering our Pro or Enterprise tiers, feel free to reach out to us directly. We're here to answer your questions and assist with upgrading your account. [Book a Demo](https://calendly.com/hello-diploi/30min) --- # Privacy > This document explains how we collect, use and protect all user data when visiting or using our platform, and defines your rights as a user. ## Privacy Policy This Privacy Policy describes how Diploi collects, uses, and discloses your personal information when you visit, use our services, or make a purchase from diploi.com (the "Site") or otherwise communicate with us (collectively, the "Services"). For purposes of this Privacy Policy, "you" and "your" means you as the user of the Services, whether you are a customer, website visitor, or another individual whose information we have collected pursuant to this Privacy Policy. Last updated October 28, 2025 --- Please read this Privacy Policy carefully. By using and accessing any of the Services, you agree to the collection, use, and disclosure of your information as described in this Privacy Policy. If you do not agree to this Privacy Policy, please do not use or access any of the Services. Diploi applies the the GDPR guidelines and regulations to all users and visitors. For more information about GDRP, check the [official europa.eu website](https://commission.europa.eu/law/law-topic/data-protection/rules-business-and-organisations_en) --- ## Data Controller **Diploi Ltd** Address: Malminkatu 30, 00100 Helsinki, Finland Business ID: FI34195512 **Contact information:** Diploi Support Team Data Protection Officer --- ## Introduction This Privacy Policy explains how Diploi Ltd (“**Diploi**,” “**we**,” “**us**,” or “**our**”) collects, use and protect your personal data when you interact with our services, website, or platforms. By using our services, you agree to the terms outlined below. **This policy applies to you if you are:** 1. A **customer** or representative of a customer (“**Customer**”) 1. A **user** of Diploi’s services (“**User**”) 1. A **prospective customer** or their representative (“**Prospect**”) 1. A representative of a **business partner** (“**Partner**”) 1. A **visitor** to our website or platforms (“**Visitor**”) **Important Notes:** 1. Diploi acts as a **data controller** for personal data processed under this policy. 1. When Customers use our services to store/process third-party data, Diploi acts as a **data processor**. In such cases, the Customer (or their client) remains the data controller. 1. We are not responsible for the privacy practices of third-party websites linked to our services. --- ## Personal Data We Collect ### (A) Customers When you sign up for our services or enter an agreement, we collect: 1. **Basic contact details**: Name, email, company name. 1. **Service-related data**: Contract details, service start/end dates, billing information (e.g., credit card details, invoices, payments) and records of interactions (e.g., support requests, feedback). **Why we need this:** To fulfill contracts, provide services and comply with legal obligations. Failure to provide required data may prevent us from delivering services. **Additional data for events/webinars:** Dietary preferences, attendance records, or topic interests (collected voluntarily during registration). ### (B) Users We collect two types of data: 1. **User Data**: Provided directly by you (e.g., name, email, billing details, communications with our team). 1. **Technical Data**: Automatically collected via cookies and analytics tools (e.g., IP address, browser type, geographic location, URLs visited). **Purpose:** To improve service functionality, personalize your experience and ensure security. Technical data may be combined with user data to enhance service delivery. ### (C) Prospect Customers We collect: 1. **Contact details**: Name, email, company name. 1. **Interaction data**: Marketing responses, webinar/event attendance, or information from public sources (e.g., LinkedIn, Discord). **Sources:** Direct submissions (e.g., contact forms), third-party lead generators, or your engagement with our content (e.g., downloading resources). ### (D) Partners We process: 1. **Basic contact information**: Name, email, phone number, company name. 1. **Interaction records**: Communications (e.g., emails, Slack messages), event registrations, or submissions via forms. **Purpose:** To manage partnerships and share relevant service updates. ### (E) Visitors We use cookies to collect: 1. **Usage data**: Pages visited, browser type, device information. 1. **Consent-based tracking**: Analytics and marketing cookies, by default consent is assumed as “denied” and we do not request or capture data that would require consent. --- ## Legal Basis for Processing We process your data based on: 1. **Contractual necessity** (e.g., delivering services). 1. **Legitimate interests** (e.g., marketing, fraud prevention). 1. **Consent** (e.g., non-essential cookies). --- ## Data Retention & Security 1. We retain data only as long as necessary for the purposes outlined here or to comply with legal obligations. 1. Data is secured using industry-standard measures (e.g., encryption, access controls). --- ## Your Rights Under GDPR, you may: 1. Access, correct, or delete your data. 1. Restrict processing or object to direct marketing. 1. Request data portability. 1. Withdraw consent (where applicable). To exercise these rights, contact us at --- ## Updates & Contact We may update this policy periodically. Changes will be posted on our website and communicated via email. --- ## Purposes and Legal Grounds for Data Processing ### (A) Customers and Users #### Purposes of Processing 1. **Service Delivery & Contractual Obligations**\ Provide access to services, manage user credentials, process payments and resolve support requests. 1. **Customer Relationship Management**\ Share updates about new features, schedule meetings, or invite you to Diploi-hosted events/webinars. 1. **Communication**\ Send service-related updates, promotional materials, or event invitations. 1. **Service Improvement**\ Analyze aggregated usage data to enhance functionality and user experience. 1. **Compliance**\ Ensure adherence to Diploi’s [Terms of Service](https://diploi.com/tos) and legal regulations. #### Legal Grounds 1. **Legitimate Interests**: Business operations, service development and marketing. 1. **Contractual Necessity**: Fulfilling obligations under customer agreements. 1. **Consent**: For optional communications (e.g., newsletters). 1. **Legal Obligations**: Reporting unlawful activities or regulatory compliance. ### (B) Prospect Customers #### Purposes of Processing 1. Generate sales leads, promote Diploi services and build brand awareness. 1. Profile Prospects based on interactions (e.g., website visits, webinar attendance, content views). #### Legal Grounds 1. **Legitimate Interests**: Business development and marketing. ### (C) Partners #### Purposes of Processing 1. Manage partnerships, share service updates and invite Partners to events/webinars. #### Legal Grounds 1. **Legitimate Interests**: Strengthening business relationships and service innovation. ### (D) Visitors #### Purposes of Processing 1. Analyze website traffic and visitor behavior. #### Legal Grounds 1. **Legitimate Interests**: Website functionality and security. --- ## International Data Transfers Personal data is stored in the EU/EEA. Transfers outside these regions occur only when necessary, such as: 1. Sharing data with Diploi’s affiliated entities or service providers (Amazon Web Services, Stripe, Linear). 1. Service health, outage triage and error logging (Sentry) **Safeguards for Transfers:** 1. EU Adequacy Decisions. 1. Binding contractual agreements requiring third parties to uphold GDPR-level protections. --- ## How We Share Personal Data ### Circumstances for Sharing Data We may share your personal data with third parties in the following situations: #### (A) Service Providers & Partners 1. Share data with third-party vendors to deliver services (e.g., payment processing, customer support tools, analytics). Eg. Partnering with **payment gateways** like Stripe or cloud storage providers like AWS. 1. Contracts with service providers and partners, ensuring compliance with GDPR and Diploi’s instructions. #### (B) Legal Compliance 1. Disclose data if required by law, including: - Law enforcement requests (e.g., court orders, subpoenas). - Reporting suspected illegal activity (e.g., fraud, security breaches). - Addressing emergencies threatening safety. 2. We will notify you of such disclosures where legally permitted. #### (C) Business Transactions 1. Share data during mergers, acquisitions, or asset sales with involved parties. #### (D) With Consent 1. Share data for purposes beyond this policy **only with your explicit consent** (revocable at any time). --- ## Data Retention We retain personal data **only as long as necessary** for the purposes outlined here or to meet legal obligations. ### (A) Users 1. Retained while your account is active. Extended retention applies for: - Legal requirements (e.g., tax laws). - Investigations into breaches of our [Terms of Service](https://diploi.com/tos). - Internal reconciliation (e.g., billing disputes). ### (B) Customers & Partners 1. Retained for the duration of the relationship and afterward for: - Legal defense or claims. - Internal reporting (e.g., financial audits). ### (C) Prospect Customers 1. Retained until deemed no longer a prospect. Databases are reviewed regularly for accuracy. ### (D) Visitors 1. **Cookies**: Manage or delete via browser settings. Non-essential cookies expire as per your consent preferences. --- ## Your Rights & Responsibilities ### Your Rights Under GDPR You have the right to: 1. **Access**: Confirm if we process your data and request a copy. 1. **Portability**: Receive your data in a structured, machine-readable format. 1. **Rectification**: Correct incomplete, outdated, or inaccurate data. 1. **Restriction**: Limit processing under GDPR Article 18 (e.g., contesting data accuracy). 1. **Erasure**: Request deletion of your data, unless legally required to retain it. 1. **Withdraw Consent**: Revoke consent for processing based on your permission. 1. **Object**: Challenge processing based on legitimate interests (GDPR Article 21). **Note**: Exercising these rights may impact our ability to provide services (e.g., deleting billing data could disrupt subscriptions). ### How to Exercise Your Rights Submit requests to: ****\ Include in your request: 1. Full name, company name (if applicable) and email. **Verification**: We may ask for additional details to confirm your identity. **Response Time**: We aim to address requests within 5 days. Repetitive or unfounded requests may be declined. ### Direct Marketing 1. **Opt-Out**: Unsubscribe using links in marketing emails. 1. **Service Communications**: Even if you opt out, we may email Customers/Users about critical service updates (e.g., outages, policy changes). ### Lodging a Complaint You may file a complaint with:\ \*\*Office of the Data Protection Ombudsman (Finland) Website: [www.tietosuoja.fi](https://tietosuoja.fi) **We encourage you to contact us first** at \[] to resolve concerns promptly. --- ## Security Measures We protect your data using: 1. **Technical Safeguards**: Encryption, firewalls, access controls. 1. **Organizational Practices**: Regular audits, staff training and secure facilities. 1. **Your Role**: Safeguard account credentials and enable **two-factor authentication (2FA)** for added security. --- ## Policy Updates Updates will be posted on our website. Material changes will be communicated in advance via email or service notifications. --- ## Contact Us For privacy inquiries or to contact our Data Protection Officer:\ **Email**: \[] --- # ToS > This is the agreement governing how users can interact with Diploi. By using the service you accept these terms of service. ## Terms of Service This website is operated by Diploi Oy. Diploi offers this website, including all information, tools and Services available from this site to you, the user, conditioned upon your acceptance of all terms, conditions, policies and notices stated here. Last updated October 28, 2025 --- ## OVERVIEW By visiting our site and/ or using our sevices, you engage in our “Service” and agree to be bound by the following terms and conditions (“Terms of Service”, “Terms”), including those additional terms and conditions and policies referenced herein and/or available by hyperlink. These Terms of Service apply to all users of the site, including without limitation users who are browsers, vendors, customers, merchants and/ or contributors of content. By accessing or using any part of the site, you agree to be bound by these Terms of Service. If you do not agree to all the terms and conditions of this agreement, then you may not access the website or use any Services. If these Terms of Service are considered an offer, acceptance is expressly limited to these Terms of Service. Any new features or tools which are added to the current service shall also be subject to the Terms of Service. You can review the most current version of the Terms of Service at any time on this page. We reserve the right to update, change or replace any part of these Terms of Service by posting updates and/or changes to our website. It is your responsibility to check this page periodically for changes. Your continued use of or access to the website following the posting of any changes constitutes acceptance of those changes. Our service is hosted on Amazon Web Services (AWS) and managed through Diploi. AWS provide us with the server infrastucture that allows us to host our platform, provision virtual machines and provide services to you. --- ### CONTACT INFORMATION Questions about the Terms of Service should be sent to us at . Diploi Ltd Address: Malminkatu 30, 00100 Helsinki, Finland Business ID: FI34195512 --- ### 1. Scope **1.1.** These Terms of Service (“**Terms**”) define your use of the services (the “**Services**”) provided by **Diploi Ltd**, a Finnish limited liability company (“**Diploi**,” “**we**,” or “**us**”). **1.2.** The Services are designed for use by businesses, organizations, professional entities for commercial purposes and for personal use. **1.3.** If you agree to these Terms on behalf of an employer or other entity, you represent that: 1. You have the legal authority to bind that entity to these Terms; 1. You have read and understood these Terms; and 1. You accept these Terms on behalf of the entity. --- ### 2. Definitions Terms below apply as defined in these Terms: **Affiliate** means an entity that directly or indirectly controls, is controlled by, or shares common control with a party (with “control” defined as more than 50% ownership of voting rights). **Control Panel** means the management interface for your subscription, accessible at **Customer** (or “**you**”) means the entity or person subscribing to the Services. **Customer Data** means all data, content, or materials uploaded, stored, or generated in the Services by you, your Users, or third parties acting on your behalf. **Credits** means prepaid credits used to pay for the Services. **End-Customer** means a client of yours to whom you provide services using Diploi’s Services. **Illegal Content** means any Customer Data violating applicable laws, including terrorist content as defined under EU Regulation 2021/784. **Service(s)** includes all Diploi-provided services, software and content, such as cloud hosting, the Control Panel and Diploi’s website. **Service Descriptions** means the technical and functional documentation for the Services, available at () **Order** means a request for Services submitted via the Control Panel, APIs, or customer support. **User** means any individual or entity accessing the Services through your account, including employees, contractors, or End-Customers. **Third-Party Products** means software, services, or components (e.g., operating systems, firewalls) not owned by Diploi but used with the Services. --- ### 3. Contractual Framework **3.1** You accept the Agreement and become bound by its terms when you: 1. Register for the Services through **Diploi’s website**; 1. Sign an order form or contract referencing these Terms; or 1. Actively use the Services. --- ### 4. Account Management **4.1** To access the Services, you must create a **primary account** (“**Account**”). You agree to provide accurate, current and complete registration details and update them promptly. **Diploi reserves the right to suspend or terminate your Account** for false, incomplete, or outdated information. **4.2** You and authorized **Users** may submit service requests (“**Orders**”) through your Account. **You are solely responsible for all Orders**, including automated or system-generated requests. Orders become binding once **Diploi delivers the requested Service**. We may impose limits on your Order submissions at our discretion. **4.3** You are liable for all activities under your Account, including User conduct. Compliance with **Diploi’s terms of service** is mandatory for you and your Users. Violations by Users will be treated as violations by you. **4.4** Safeguard your Account credentials. Notify **Diploi immediately** if unauthorized access is suspected. We may suspend your Account temporarily to mitigate security risks. --- ### 5. License to Use **5.1** Subject to compliance with these Terms, **Diploi grants you a non-exclusive, non-sublicensable, revocable license** to access the Services for internal business purposes during the Agreement term. **5.2** You may use the Services to support your **End-Customers**, but you remain fully responsible for their actions and content. **Diploi assumes no liability or obligations to your End-Customers.** --- ### 6. Service Delivery & Warranties **6.1** **Diploi will provide the Services** with commercially diligent efforts and in material alignment with the **Service Documentation**. **6.2** Report service deficiencies to **Diploi in writing** via email within 14 days of discovery. Include detailed descriptions of the issue. **6.3** **Diploi will attempt to resolve deficiencies** but retains discretion to terminate the affected Service if remediation is impractical. **6.4** Except as stated herein, the Services are provided **“as-is”** with no warranties express, implied, or statutory including fitness for purpose, merchantability, or non-infringement. --- ### 7. Technical Assistance **7.1** **Diploi provides support** to the Users who initiate a request for support. Contact methods supported by Diploi include Discord for issues that do not require private information disclosures and via email to for issues that require disclosure of private information. --- ### 8. Third-Party Integrations **8.1** Use of third-party software, tools, or services (“**Third-Party Products**”) in connection with Diploi’s Services is governed by their respective licenses and terms. **Diploi assumes no liability** for Third-Party Products, including their functionality, compliance, or security, even if integrated with our Services. --- ### 9. Service Enhancements **9.1** **Diploi may update, modify, or discontinue Services** to improve performance, security, or compliance. Changes will not materially degrade core functionalities. **9.2** For changes with **material adverse effects**, Diploi will notify you **30 days in advance**, during which you may terminate the affected Service. --- ### 10. Pricing & Taxes **10.1** Service fees are based on usage and displayed in and your **Control Panel**. Billing defaults to **hourly increments** unless otherwise agreed. **10.2** Prices **exclude VAT and applicable taxes**, and will be added to the billing sum, unless stated otherwise. **10.3** Diploi reserves the right to adjust prices with **30 days’ prior notice**. --- ### 11. Payment & Credits **11.1** Services are billed **based on usage** at least once a month afterwards. Invoices are **available for download in the Control Panel**. **11.2** If the platform is **not able to charge** your chosen method of payment, **the Account is suspened immediately**. If **amount due is unpaid for 14 days**, the platform has the right to take actions to **terminate Account and delete Customer Data**. **Fees accrue during suspension until termination**. **11.3** Diploi may initiate charges or pre-authorizations **at any time** to confirm that your Account maintains sufficient funds or credit to cover existing or upcoming usage. These checks may occur without advance notice and can be repeated as needed. **11.4** For **new Accounts** or situations where additional verification is required to prevent abuse or fraud, Diploi may **charge, partially charge, or place holds** on your payment method before or during access to the Services. The amount, timing and frequency of such measures are determined at Diploi’s discretion. --- ### 12. Trial Periods **12.1** **Free Trials** may be offered at Diploi’s discretion, with limited features, free credits or duration. Eligibility criteria apply and Diploi may modify or withdraw Trials without liability. **12.2** Payment details may be required to start a Trial. Post-Trial, Services auto-renew at standard rates unless canceled via before expiry. **12.3** If a Trial expires and you have not added a valid payment method in the Control Panel, Diploi will delete your Account (including any associated Customer Data) without further notice. Access to the Services thereafter requires creating a new Account with compliant billing details. --- ### 13. Compliance & Enforcement **13.1** You agree to use the Services lawfully and in compliance with these Terms. **Diploi reserves the right to act** if we suspect violations or receive legal orders regarding Illegal Content, including: 1. Temporarily suspending your Account; 1. Terminating the Agreement for material or repeated violations; 1. Removing or restricting access to Illegal Content without prior notice if legally mandated. **13.2** You must cooperate with investigations into potential breaches of this Agreement. **13.3** **Diploi assumes no liability** for suspensions, terminations, or content removal under this Section. --- ### 14. Prohibited Activities **14.1** The Services must not be used for unlawful, harmful, or abusive purposes. Prohibited actions include, but are not limited to: 1. **Intellectual Property Violations:** Copying, redistributing, or reverse-engineering the Services without authorization. 1. **System Abuse:** Overloading, disrupting, or mining data from Diploi’s infrastructure. 1. **Fraud & Spam:** Transmitting unauthorized ads, malware, or mass communications. 1. **Impersonation:** Creating accounts for others without consent. 1. **Criminal Activity:** Engaging in illegal acts or violating third-party rights (e.g., privacy, trade secrets). --- ### 15. Liability & Indemnification **15.1** **Diploi’s IP Infringement Defense:** If the Services infringe a third party’s intellectual property rights, Diploi will defend you against claims and cover court-awarded damages, provided you: 1. Notify us in writing within **30 days** of the claim; 1. Grant us sole control over the defense; 1. Provide reasonable assistance. **15.2** **Remedies for Infringement:** Diploi may, at its option: 1. Modify the Services to resolve the issue; 1. Procure a license for your continued use; or 1. Terminate the Agreement and refund prorated fees. **15.3** **Exclusions:** Diploi is not liable for claims arising from: 1. Modifications by you, Users, or third parties; 1. Use with non-Diploi products; 1. Failure to use the latest Service version; 1. Activities unrelated to the Services. **15.4** **Customer Indemnification:** You will defend and indemnify Diploi against claims resulting from your breach of these Terms, including: 1. Damages, liabilities and legal costs incurred by Diploi; 1. Settlements approved by you. --- ### 16. Data Ownership & Responsibilities **16.1** You retain all rights to **Customer Data** uploaded to the Services. By using the Services, you grant **Diploi** a non-exclusive license to process, store and transmit your data solely to deliver the Services. You are solely responsible for the legality, accuracy and rights clearance of your data. **Diploi will delete all Customer Data** within 60 days after termination, unless legally required to retain it. **16.2** Diploi assumes no liability for opinions or non-personal data within Customer Data. **16.3** Do not upload **Illegal Content**, infringing material, or data violating third-party rights. **16.4** You must maintain **external backups** of Customer Data. Diploi is not responsible for data loss. --- ### 17. Confidentiality Obligations **17.1** “**Confidential Information**” includes non-public data exchanged under this Agreement (e.g., business strategies, technical details). Both parties agree to: 1. Limit access to personnel needing it for the Agreement; 1. Protect confidentiality using reasonable measures. **17.2** Exceptions to confidentiality include publicly available information or independently developed data. **17.3** If legally compelled to disclose, notify the disclosing party unless prohibited. Post-termination, destroy or return Confidential Information, retaining only legally mandated or backup copies. --- ### 18. Intellectual Property **18.1** Diploi retains all rights to the Services, including software, trademarks and aggregated usage data. You grant Diploi a perpetual, royalty-free license to use **feedback or suggestions** to improve the Services. **18.2** Third-party software integrated with the Services is governed by its respective licenses. --- ### 19. Liability Limits **19.1** Neither party is liable for **indirect damages** (e.g., lost profits, reputational harm). **19.2** Diploi’s total liability is capped at the **lesser of**: 1. Fees paid in the prior 6 months; or 1. €10,000. **19.3** Exclusions: Liability caps do not apply to gross negligence, intentional misconduct, or breaches of these terms. **19.4** Claims must be filed within 90 days of the incident. --- ### 20. Unforeseen Events **20.1** “**Force Majeure**” includes pandemics, cyberattacks, or government actions delaying performance. Affected parties may suspend obligations without penalty. **20.2** If Force Majeure lasts over 60 days, either party may terminate the Agreement. --- ### 21. Compliance with Laws **21.1** You agree to comply with **EU, U.S. and Finnish export/sanctions laws**. We prohibit use of our services in embargoed/sanctioned regions (e.g., Crimea, North Korea). **21.2** No User, Customer or End-Customer under sanctions is allowed to use Diploi’s Services. Diploi reserves the right to suspend or terminate accounts affected by sanctions. --- ### 22. Publicity & Case Studies **22.1** Diploi may request to use your **name/logo** in marketing materials, subject to your written approval. **22.2** Participation in case studies is voluntary. Approved case studies may be published on Linkedin, Discord, Github, Google, Dev.to and websites owned by Diploi. --- ### 23. Termination Rights **23.1** You may terminate this Agreement **for any reason** with **5 days’ written notice**. Diploi may terminate with **30 days’ written notice**, except under fixed-term contracts, which are governed by their specific terms. --- ### 24. Termination for Breach Either party may terminate immediately if the other: 1. **Materially breaches** the Agreement and fails to remedy it within **10 business days** of written notice; 1. Becomes **insolvent**, enters liquidation, or fails to pay debts. --- ### 25. Agreement Integrity & Changes **25.1** This Agreement constitutes the **entire understanding** between the parties. **25.2** Amendments require **written consent**. Diploi may update Terms by posting revisions on . For **material changes**, we will notify you **30 days in advance**, allowing termination rights. **Legal-mandated changes may take effect immediately.** --- ### 26. Waiver Policy A party’s failure to enforce a term does not waive future rights. Waivers must be **in writing**. --- ### 27. Transfers & Third Parties **27.1** Neither party may assign the Agreement without prior consent, except: 1. Diploi may transfer rights to **Affiliates** or during mergers/acquisitions; 1. Diploi may use subcontractors but remains responsible for their performance. **27.2** Your obligations benefit Diploi’s **Affiliates, subcontractors and personnel**. No third-party rights are otherwise created. --- ### 28. Partial Invalidity If a clause is deemed unenforceable, the rest of the Agreement remains valid. Parties will negotiate replacement terms reflecting the original intent. --- ### 29. Legal Notices **29.1** Notices must be: 1. Emailed to . 1. Sent via **registered mail** to Diploi Ltd, Malminkatu 30, 00100 Helsinki; or **29.2** **Illegal Content reports** under the EU Digital Services Act (Regulation 2022/2065 of 19 October 2022) (“DSA Notice”) must be submitted to and include: 1. Reason for illegality; 1. Data location (e.g., URL); 1. Submitter’s contact details. --- ### 30. Dispute Resolution **30.1** The Agreement is governed by **Finnish law**, excluding conflict-of-law principles. Disputes are resolved via **arbitration** under the Arbitration Rules of the Finland Chamber of Commerce in Helsinki, in English. **30.2** Diploi may pursue unpaid debts in courts of your jurisdiction. ---