Marky website builder
Marky can plan, code, preview and publish a website—or build the backend, database and account flows when the idea needs real application logic.
Direct answer
Marky is a conversational website and web app builder inside Easy-Peasy.AI. It can generate an editable React and TypeScript project, run a live preview, add an Express backend, Neon Postgres, authentication and file storage, then publish the approved version to Google Cloud Run. You can keep iterating in chat or sync the code to GitHub.
Start with your workflow
Each guide below explains the records, account flows and edge cases that matter for that product—not just a different visual template.
Multi-user products with accounts, dashboards, APIs and persistent application data.
Branded spaces for projects, files, approvals, invoices and client-specific updates.
Service pages, staff availability, reservation records and an operator schedule.
Member login, gated libraries, tiers, progress and community-oriented dashboards.
Searchable listings, categories, submissions, moderation and map-ready data.
CRUD workflows, inventory, approvals, reports and team-specific operations screens.
Choose the right scaffold
Marky can start light and add the application layer when the project needs accounts, stored records or protected server logic.
| Capability | Simple website | Full-stack app |
|---|---|---|
| Frontend | Vite, React, TypeScript and Tailwind CSS | Vite, React, TypeScript and Tailwind CSS |
| Server | Not included | Express with typed tRPC APIs |
| Database | Not included | Managed Neon Postgres with Drizzle |
| User accounts | Not included | Better Auth foundation and Google OAuth support |
| File uploads | Static project assets | Cloudflare R2, using an S3-compatible API |
| Best for | Marketing sites, portfolios and information pages | Portals, SaaS, directories and operational apps |
Production foundation
The chat is the interface. Underneath it, Marky works with a conventional codebase and managed services you can reason about.
Complete capability map
Capabilities are selected from the brief. A brochure site does not need a database; a portal does. Marky can add the deeper layers when the product actually calls for them.
The working code and feedback loop
Persistent application data and identity
Protected credentials and external capabilities
Versions, domains and production operation
Build loop
Give Marky the users, core workflow, records and visual direction—not just a page count.
Marky scaffolds the project, runs it and opens a URL you can inspect while the conversation continues.
Request changes in plain language and save a named working version before larger revisions.
Approve production deployment, choose the URL and optionally connect the codebase to GitHub.
Clear boundaries
Questions, answered
Yes. Marky can start with a lightweight React website or create a full-stack web app with an Express backend, typed APIs, a Neon Postgres database, Drizzle models, authentication, file storage, and server-side integrations. The scaffold is chosen from the requirements in your brief.
Yes. Full-stack projects include an authentication foundation and support a centralized Google OAuth flow. Marky can build the sign-in screens and authenticated product experience, then test the flow in preview before the app is published.
The built-in production publishing flow deploys websites and web apps to Google Cloud Run. Every published project can use an editable easy-peasy.site subdomain, connect an existing custom domain, or purchase a new domain through the project settings.
Google Cloud Run is Marky's built-in deployment target. Because the generated project is a real TypeScript and Node.js codebase that can be pushed to GitHub, a developer can adapt it for AWS. AWS services and credentials are an integration path, not the default one-click publish flow.
You can connect GitHub, create a new repository or link an existing one, and push the project code and later changes. Marky also keeps preview checkpoints so you can inspect versions and roll the editable project—or an eligible live deployment—back to an earlier state.
Yes. Marky can upgrade a static web project to the full-stack scaffold when the site grows to need user accounts, stored records, backend APIs, uploads, or AI features. The upgrade provisions the database and authentication foundation without requiring a brand-new conversation.
Start with a useful brief