Turn raw site photos into high-fidelity landscape proposals in seconds. Lawnscape AI is a visual tool for architectural studios to draft, compare, and render landscape concepts from a single site photo.
A recorded walkthrough is available as a demo video.
- Studio Composer — upload a site photo and draft a landscape vision with AI.
- Comparison slider — interactive before/after view to show clients the value.
- One-click proposals — generate photorealistic renders from a draft.
- Responsive — works on mobile for on-site presentations.
Built to feel like a high-end Italian architectural studio rather than a generic SaaS tool. Space Grotesk for headings, Satoshi for UI, olive green (#4A5D23) accents on warm cream (#F4F4F0), with glassmorphism and smooth scrolling via Lenis.
git clone https://github.com/TechTronixx/Lawnscape-ai.git
cd Lawnscape-ai
bun install
cp .env.example .env # then put your Krea token in .env
bun run devOpen http://localhost:5173.
- Clone:
git clone https://github.com/TechTronixx/Lawnscape-ai.git - Enter the directory:
cd Lawnscape-ai - Install dependencies:
bun install - Copy the env template:
cp .env.example .env - Add your Krea token to
.env - Start the dev server:
bun run dev
Open the app, drop a site photo into the Studio Composer, describe the landscape you want, and generate. Use the comparison slider to preview before/after, then export the proposal render.
The app reads one env var, set in .env at the project root:
VITE_KREA_API_TOKEN=your_token_hereVITE_KREA_API_TOKEN— your Krea.ai API token. Get one at https://www.krea.ai/settings/api-tokens. TheVITE_prefix is required; Vite only exposes prefixed vars to the client.
- Writes a
.envfile locally with your API token. Never commit.env— it is gitignored. - Image generation routes through the Krea.ai API, a third-party service subject to Krea's terms and rate limits.
VITE_-prefixed env vars are bundled into the client. In any deployed build the Krea token is exposed to the browser. For production, proxy Krea calls through a backend so the token stays server-side.- The dev server runs on port 5173.
bun run lint # eslint
bun run build # tsc -b && vite build
bun run preview # preview the production buildWork on the development branch and open pull requests there. See CONTRIBUTING.md for the branch workflow and review gates.
Pull requests are welcome. Open an issue first to discuss major changes, and read CONTRIBUTING.md before submitting.
Lawnscape AI writes a .env file containing a VITE_KREA_API_TOKEN and sends site photos and prompts to the Krea.ai API for image generation. You are responsible for complying with Krea.ai's terms of service and for any data you submit. Because VITE_ env vars are client-bundled, a deployed build exposes the token to end users — do not ship a production build without a server-side proxy if token secrecy matters. The software is provided "AS IS", without warranty of any kind.
MIT — Copyright (c) 2026 TechTronixx.