Can I vibecode Appsmith Cloud?

Build a personal replacement for Appsmith Cloud in an empty repository.
Use Next.js 15, TypeScript, Tailwind CSS, PostgreSQL, Drizzle ORM, and Docker Compose to wire it all together; do not offer alternative stacks or languages.
The core loop is: define tables and views, compose an internal dashboard from a database and a fixed widget library, connect one approved data source, and deploy it for a small trusted team. Do not aim to be a general platform; focus on deep, reliable implementation of this specific core loop.
Ensure the first run works locally with a single documented command (e.g., `docker compose up --build`).
Store all user data locally by default, avoiding any external SaaS dependencies for core functionality, and make data export straightforward via a dedicated API endpoint or script in standard formats like CSV or JSON.
Put all secrets, API keys, and database credentials in a `.env` file, ship a `.env.example`, and implement pre-commit hooks or CI checks to ensure credentials are never accidentally committed to version control.
Create a comprehensive schema editor for text, number, boolean, date, enum, and relation fields. Generate robust list, detail, create, edit, and kanban views directly from the defined schema.
Store every schema definition, widget configuration, and dashboard layout in the local database for auditability and durability.
Design all side effects to be idempotent and resilient. Implement role-based read and write rules for admin and member roles reliably.
Build in rate limiting, exponential backoff for API errors in the REST connector, and a mechanism for secret rotation of encrypted credentials.
Ship a complete Docker Compose setup with health checks for all services, migrations, a seeded example workspace, comprehensive test suites, database backup scripts, and clear documentation.
Design a minimal but polished web UI with clear states for empty, loading, success, and recoverable errors, ensuring accessible keyboard navigation, focus states, and sensible contrast.
Implement strict input validation using modern libraries (like Zod), enforce safe data handling, safe filenames, and gracefully handle unavailable APIs without crashing the application.
Write focused unit tests for the core logic, schema generation, and at least one robust end-to-end happy path test using an automated testing framework.
Create an exhaustive README detailing the setup process, system architecture, permission models, data storage locations, backup/restore steps, and limitations.
Strictly avoid adding multi-tenant user accounts, billing systems, telemetry, tracking analytics, or any hosted control plane.
Deliberately leave out arbitrary user-authored code execution (no eval blocks).
Deliberately leave out a broad integration marketplace; strictly support one REST connector.
Deliberately leave out native mobile binaries and enterprise compliance frameworks.
Finish by running the test suite, building the application, and outputting the exact commands used to verify the system. Fix errors rather than merely describing them.