The builder
Paste the URL of the site you already have and we import and modernize it, or describe the site you need and the builder writes it straight into a private repository in your own GitHub account. No proprietary editor, no lock-in, and an exit that is always one git clone away. A static build can run fully disconnected from DevGhouse data, forever.
The onboarding funnel showing the import path beside the build path with its static and database-driven modes
Inside the builder
Import a URL
Paste the URL and Websites pulls in your pages, your brand assets, and your metadata, then rebuilds them on the platform. Your site stops aging the day you connect it, and you keep the content you already wrote.
A site URL pasted into the funnel with its extracted pages, brand, and metadata
Describe a new site
Tell the builder what your business does and what the site needs to achieve. There is no drag-and-drop canvas to learn, because describing the outcome is the interface.
The build path with a plain-language brief describing a new site
Static mode
Static builds are generated from your details, and connecting GitHub creates a private repository in your own account holding the finished build. Host it anywhere you like, or deploy it to Vercel in one click from the dashboard and get a live URL back. Hand-edit it whenever the AI is not enough.
A static build landing as a private repository in a personal GitHub account
Database-driven mode
A database-driven site consumes the platform content rails over its website token, so page meta, blog, forms, and products stay editable from the dashboard and by your routines. Nothing needs a deploy to change.
A database-driven site pulling its meta, blog, forms, and products from the rails
GitHub connection
Your GitHub connection is personal and follows you into whatever realm you work in, so a repo is created in your account rather than a company vault you cannot reach. Link one repo or many, set a role per repo, and let teammates request access.
The Code tab with several linked repositories and their per-repo roles
Common questions
You do. A build creates a private repository in your own GitHub account, and you can clone it whenever you like.
Yes. A static build is real source in your own repo, so there is no proprietary editor standing between you and the code.
Static is generated from your information into your own repo and hosted anywhere. Database-driven consumes the platform content rails over its token, so the dashboard and routines keep editing it live. The mode toggle arrives with the builder slice; today a new build lands as owned source in your GitHub.
No. Importing extracts your pages, brand, and metadata and rebuilds them on the platform, so your content comes with you.
No. The GitHub connection is always your own and follows you into whatever realm you work in.
Your code, your account
Import a URL or describe a brief. Both land as a real website record in your dashboard, and a build lands as a private repo in your own GitHub.
Start your website