Markyウェブサイトビルダー
Markyはウェブサイトの設計、実装、プレビュー、公開に加え、実際のアプリロジックが必要な場合はバックエンド、データベース、アカウントフローまで構築できます。
簡潔な回答
MarkyはEasy-Peasy.AI内の対話型サイト・Webアプリビルダーです。編集可能なReactとTypeScriptプロジェクトを生成し、ライブプレビュー、Express、Neon Postgres、認証、ファイル保存を追加して、承認した版をGoogle Cloud Runへ公開できます。チャットで改良を続けることも、GitHubと同期することも可能です。
ワークフローから始める
各ガイドでは、見た目のテンプレートだけでなく、その製品に必要なデータ、アカウントフロー、例外ケースを解説します。
最適な構成を選ぶ
Marky can start light and add the application layer when the project needs accounts, stored records or protected server logic.
| 機能 | シンプルなウェブサイト | フルスタックアプリ |
|---|---|---|
| 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 |
本番運用の基盤
The chat is the interface. Underneath it, Marky works with a conventional codebase and managed services you can reason about.
機能の全体像
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
構築サイクル
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.
明確な前提
よくある質問
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.
具体的な要件から始めましょう
