Coderblock Now Supports One-Click Production Deploys

From conversation to production in one click

Coderblock is introducing one-click production deployments, making it easier to turn an app built and refined through chat into a live product that is ready to share.

During development, every project has a live preview at an <app>.coderblock.dev address. When the app is ready, simply select Publish to create a production version at a dedicated <app>.coderblock.app address, with SSL included. You can also connect a custom domain directly to the project.

The result is a seamless workflow from idea to launch, without having to export the app, manually configure a hosting service, or set up deployment infrastructure separately.

From idea to published app

The creation process in Coderblock starts with a natural-language description, a product template, or an existing project. The AI generates the application and lets you modify it through conversation. For example, you can ask:

• “Add login and protect the account page.”
• “Create an admin dashboard.”
• “Add a bookings table.”
• “Let customers pay for a monthly subscription.”
• “Improve the dashboard layout on mobile.”

Throughout the process, you can review every change in the live preview. Once the result meets the project’s requirements, Publish moves the latest approved version to the production environment.

There is no need to switch to an external deployment service or manually recreate the app’s infrastructure. The project stays within the same Coderblock environment throughout every stage: creation, development, testing, and publishing.

A true full-stack deployment

Deployment is not limited to the frontend interface. Coderblock applications can include a real backend, database, authentication, storage, and server-side functions. For standard web applications, the frontend uses React, Vite, TypeScript, and Tailwind CSS, while every project has a dedicated Supabase environment with Postgres, Auth, Storage, Row Level Security, and Deno Edge Functions.

This makes it possible to publish applications that use real data and logic, rather than just static pages or visual prototypes.

For example, a booking app can include:

• user accounts and authentication;
• persistent availability and bookings;
• roles and permissions;
• admin dashboards;
• data protected by Row Level Security;
• backend functions;
• payments and subscriptions.

Before publishing, project resources can be reviewed from the Backend tab, where tables, authenticated users, storage, and functions are available.

Publish on your own domain

Every published application automatically receives a production address at <app>.coderblock.app. For users who want a more customized identity, Coderblock also supports custom domains. From Settings → Domains, you can:

Connect an existing domain

If you already own a domain, you can connect it to the project by following the guided DNS configuration instructions.

Buy a domain directly through Coderblock

You can also purchase a new domain directly within the platform. In this case, checkout, DNS configuration, and SSL are handled directly by Coderblock. In both cases, the SSL certificate is included with publishing.

Keep building after launch

Deployment is not the end of the development process. After publishing an app, you can return to the project and continue modifying it through chat. For example, you can ask:

“Add a date filter to the admin dashboard.”

or:

“Add a phone number field to user profiles.”

Changes can be reviewed again in the development preview before being published. Subsequent releases use hot updates, allowing approved changes to reach production quickly without manually repeating the entire deployment process. This creates a simple workflow: Build → Preview → Test → Publish → Iterate

From chat to a truly live app

One-click deployment completes the core Coderblock workflow. The goal is not just to help you generate code or create a prototype, but to let you go from describing an idea to launching a real application within a single workspace. You can start from scratch, use a template, build the product through chat, test it in the live preview, and publish it when it is ready.

One idea. One conversation. One live app.