Vibecode One Place

track this build5 steps, step by step

NOT REALLY · don't bother

price $45.06/moyou'd save $540.72/yrbuild time multi-weekcategory 🔍 ai searchreplaced by 0 people

You can build a scheduled personal property monitor, but not One Place: the value is the maintained real-estate corpus, crawler fleet, AI extraction, deduplication, image/semantic search, geo enrichment, and constant source upkeep across millions of listings.

the project pack4 files · fastest path to a working personal build

You are building a lean indie version of One Place.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# One Place indie build

## Goal

Build the smallest trustworthy replacement for the core One Place workflow for one developer or a tiny team.

## Scope

Run saved searches on a schedule, crawl configured source pages, use an LLM API key to extract listing fields, dedupe into SQLite, email matching finds, and expose an MCP server for chat/coding agents.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- millions of already-normalized listings
- maintained crawlers across real-estate portals
- AI extraction, deduplication, and image/semantic search at scale
- geo/POI enrichment and currency/unit normalization
- hosted boards, lead pipeline, sharing, and agentic search

If those capabilities are essential, use One Place instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Build me a scheduled personal property monitoring agent, the honest consolation
build for One Place: it watches the sources I configure, it does not rebuild a
live nationwide real-estate index. Requirements:

- Node + Express + better-sqlite3 on localhost:4920, with a small web UI for saved
searches, matches, and lead notes.
- Saved searches live in SQLite: name, source URLs, natural-language criteria, hard
filters, cadence, email recipients, and last-run time.
- A node-cron runner wakes on each cadence, fetches configured source/search pages with
Playwright, and stores raw HTML snapshots for debugging.
- Send cleaned listing HTML to an LLM API key from .env and extract strict JSON: title,
price, currency, surface, rooms, location text, description, image URLs, source URL, and
confidence.
- Match each extracted listing against the saved search criteria with deterministic
filters first, then an LLM yes/no explanation for fuzzy preferences like renovation
potential or sea view.
- Store listings and match decisions in SQLite, dedupe by canonical URL first and fuzzy
title+price+surface+location second; keep price-change history.
- Email new matches via Resend or SMTP creds in .env, including the match reason, key
fields, source link, and unsubscribe/disable link for that saved search.
- Include an MCP server exposing tools: list_saved_searches, run_search_now,
get_recent_matches, explain_match, update_search, and add_lead_note, so Claude/Codex can
operate it from chat.
- No accounts, no telemetry, binds to localhost only. Out of scope: nationwide coverage,
anti-bot arms races, paid data resale, mobile apps, and collaborative CRM.
- README: crawler ethics, robots/terms warning, required API/email keys, how to run the
scheduler, and how to connect the MCP server.

## Required capabilities

- cron-style scheduled search runner
- Playwright scraping
- LLM API key for listing extraction
- SMTP or Resend email alerts
- MCP server for agent access

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a lean indie version of One Place.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# One Place indie build

## Goal

Build the smallest trustworthy replacement for the core One Place workflow for one developer or a tiny team.

## Scope

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

If those capabilities are essential, use One Place instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

## Required capabilities

- cron-style scheduled search runner
- Playwright scraping
- LLM API key for listing extraction
- SMTP or Resend email alerts
- MCP server for agent access

## Delivery order

## Done when

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a production product version of One Place.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== PRODUCT.md =====
# One Place product brief

## Problem

You can build a scheduled personal property monitor, but not One Place: the value is the maintained real-estate corpus, crawler fleet, AI extraction, deduplication, image/semantic search, geo enrichment, and constant source upkeep across millions of listings.

## Product outcome

Run saved searches on a schedule, crawl configured source pages, use an LLM API key to extract listing fields, dedupe into SQLite, email matching finds, and expose an MCP server for chat/coding agents.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- cron-style scheduled search runner
- Playwright scraping
- LLM API key for listing extraction
- SMTP or Resend email alerts
- MCP server for agent access

## Explicit non-goals for v1

- millions of already-normalized listings
- maintained crawlers across real-estate portals
- AI extraction, deduplication, and image/semantic search at scale
- geo/POI enrichment and currency/unit normalization
- hosted boards, lead pipeline, sharing, and agentic search

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

===== ARCHITECTURE.md =====
# Architecture

## Starting brief

Build me a scheduled personal property monitoring agent, the honest consolation
build for One Place: it watches the sources I configure, it does not rebuild a
live nationwide real-estate index. Requirements:

- Node + Express + better-sqlite3 on localhost:4920, with a small web UI for saved
  searches, matches, and lead notes.
- Saved searches live in SQLite: name, source URLs, natural-language criteria, hard
  filters, cadence, email recipients, and last-run time.
- A node-cron runner wakes on each cadence, fetches configured source/search pages with
  Playwright, and stores raw HTML snapshots for debugging.
- Send cleaned listing HTML to an LLM API key from .env and extract strict JSON: title,
  price, currency, surface, rooms, location text, description, image URLs, source URL, and
  confidence.
- Match each extracted listing against the saved search criteria with deterministic
  filters first, then an LLM yes/no explanation for fuzzy preferences like renovation
  potential or sea view.
- Store listings and match decisions in SQLite, dedupe by canonical URL first and fuzzy
  title+price+surface+location second; keep price-change history.
- Email new matches via Resend or SMTP creds in .env, including the match reason, key
  fields, source link, and unsubscribe/disable link for that saved search.
- Include an MCP server exposing tools: list_saved_searches, run_search_now,
  get_recent_matches, explain_match, update_search, and add_lead_note, so Claude/Codex can
  operate it from chat.
- No accounts, no telemetry, binds to localhost only. Out of scope: nationwide coverage,
  anti-bot arms races, paid data resale, mobile apps, and collaborative CRM.
- README: crawler ethics, robots/terms warning, required API/email keys, how to run the
  scheduler, and how to connect the MCP server.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

===== AGENTS.md =====
# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

===== MILESTONES.md =====
# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

===== OPERATIONS.md =====
# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted One Place capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

README.md

# One Place indie build

## Goal

Build the smallest trustworthy replacement for the core One Place workflow for one developer or a tiny team.

## Scope

Run saved searches on a schedule, crawl configured source pages, use an LLM API key to extract listing fields, dedupe into SQLite, email matching finds, and expose an MCP server for chat/coding agents.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- millions of already-normalized listings
- maintained crawlers across real-estate portals
- AI extraction, deduplication, and image/semantic search at scale
- geo/POI enrichment and currency/unit normalization
- hosted boards, lead pipeline, sharing, and agentic search

If those capabilities are essential, use One Place instead of pretending the gap is solved.

AGENTS.md

# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

BUILD_PLAN.md

# Build plan

## Original build brief

## Required capabilities

- cron-style scheduled search runner
- Playwright scraping
- LLM API key for listing extraction
- SMTP or Resend email alerts
- MCP server for agent access

## Delivery order

## Done when

.env.example

# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

PRODUCT.md

# One Place product brief

## Problem

You can build a scheduled personal property monitor, but not One Place: the value is the maintained real-estate corpus, crawler fleet, AI extraction, deduplication, image/semantic search, geo enrichment, and constant source upkeep across millions of listings.

## Product outcome

Run saved searches on a schedule, crawl configured source pages, use an LLM API key to extract listing fields, dedupe into SQLite, email matching finds, and expose an MCP server for chat/coding agents.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- cron-style scheduled search runner
- Playwright scraping
- LLM API key for listing extraction
- SMTP or Resend email alerts
- MCP server for agent access

## Explicit non-goals for v1

- millions of already-normalized listings
- maintained crawlers across real-estate portals
- AI extraction, deduplication, and image/semantic search at scale
- geo/POI enrichment and currency/unit normalization
- hosted boards, lead pipeline, sharing, and agentic search

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

ARCHITECTURE.md

# Architecture

## Starting brief

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

AGENTS.md

# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

MILESTONES.md

# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

OPERATIONS.md

# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted One Place capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

$ choose a build depth, inspect the files, then open the complete pack in your agent

why people still pay

They pay because property search is a moving data pipeline: portals block scrapers, listing HTML changes, duplicates multiply, and the useful part is having the whole market normalized and searchable before a deal disappears.

what you lose

xmillions of already-normalized listings

xmaintained crawlers across real-estate portals

xAI extraction, deduplication, and image/semantic search at scale

xgeo/POI enrichment and currency/unit normalization

xhosted boards, lead pipeline, sharing, and agentic search

prior art · use these instead of building, if you'd rather

Nothing worth pointing at. That's why the prompt exists.

share on X ↗"I just replaced One Place ($45.06/mo) with one prompt"

the numbers

One Place pricing

plan	monthly	annual (per mo)	what you get
free	$0	$0	Unlimited search, favorites, saved searches and alerts; maximum 5 boards.
pro	$45.06	—	Unlimited boards plus lead pipeline, activity tracking and agentic search.

free tierUnlimited search, favorites, saved searches and alerts, capped at 5 boards.

billingmonthly price published; annual option exists but its current amount was not recoverable; cancel or downgrade without commitment; VAT extra

hidden costsVAT is added where applicable. The annual discount/price was present behind a selector but not independently verifiable, so it is left null.

verified 2026-08-11 · source ↗

questions

Is One Place free?

The free plan gives unlimited search and saved searches, capped at 5 boards. Paid is Pro at $45.06/mo (checked 2026-08-11).

Vibecode One Place

Not really. One Place's value is not the code: The market-wide index is the product. See the honest breakdown above.

How much does One Place cost?

One Place costs about $45.06/month (Pro, checked 2026-08-11), which is $540.72 per year.

What do I lose by replacing One Place?

Honestly: millions of already-normalized listings; maintained crawlers across real-estate portals; AI extraction, deduplication, and image/semantic search at scale; geo/POI enrichment and currency/unit normalization; hosted boards, lead pipeline, sharing, and agentic search. If any of those are load-bearing for you, keep paying.

Is there an open-source alternative to One Place?

No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.