Vibecode Point.me
track this build5 steps, step by step0%NOT REALLY · don't bother
price $10.75/moyou'd save $129/yrbuild time closest consolation build: one sittingcategory ✈️ travelreplaced by 0 people
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Point.me, store manually researched award options and compare user-entered points values. The hard boundary is live award inventory search, airline program integrations, data operations, and concierge expertise, plus proprietary live data and network coverage.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Point.me. 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 ===== # Point.me indie build ## Goal Build the smallest trustworthy replacement for the core Point.me workflow for one developer or a tiny team. ## Scope Store manually researched award options, compare user-entered points values, map places and reservations, and keep an offline itinerary without claiming live proprietary availability. ## 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: - live award inventory search, airline program integrations, data operations, and concierge expertise - live fare and inventory data - global routing dataset - crowdsourced trail intelligence - booking, disruption support, and offline map fleet If those capabilities are essential, use Wanderer 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 a closest honest personal substitute for Point.me in an empty repository. Use Next.js 15, TypeScript, SQLite, MapLibre GL, and user-supplied map and travel APIs; do not offer alternative stacks. The core loop is: store manually researched award options, compare user-entered points values, map places and reservations, and keep an offline itinerary without claiming live proprietary availability. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create trips, days, places, reservations, notes, documents, packing items, and emergency contacts. Geocode only user-entered places and display them through MapLibre with cached trip-area tiles where allowed. Parse forwarded reservation text locally into editable fields without logging message content. Build a day timeline, route overview, conflict warnings, timezone display, and offline printable itinerary. Allow manual updates for delays and reservations and label all external data with source and timestamp. Export a complete trip bundle as JSON, calendar file, Markdown, and PDF. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure. Deliberately leave out live flight, hotel, award, or ticket inventory. Deliberately leave out commercial turn-by-turn navigation and global offline maps. Deliberately leave out booking guarantees, disruption rebooking, and traveler support. Finish by running the tests and listing the exact commands used. ## Required capabilities - modern browser - MapTiler or compatible map key - user-entered reservations - optional public transit or weather API ## 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 Point.me. 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 ===== # Point.me indie build ## Goal Build the smallest trustworthy replacement for the core Point.me workflow for one developer or a tiny team. ## Scope Store manually researched award options, compare user-entered points values, map places and reservations, and keep an offline itinerary without claiming live proprietary availability. ## 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: - live award inventory search, airline program integrations, data operations, and concierge expertise - live fare and inventory data - global routing dataset - crowdsourced trail intelligence - booking, disruption support, and offline map fleet If those capabilities are essential, use Wanderer 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 a closest honest personal substitute for Point.me in an empty repository. Use Next.js 15, TypeScript, SQLite, MapLibre GL, and user-supplied map and travel APIs; do not offer alternative stacks. The core loop is: store manually researched award options, compare user-entered points values, map places and reservations, and keep an offline itinerary without claiming live proprietary availability. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create trips, days, places, reservations, notes, documents, packing items, and emergency contacts. Geocode only user-entered places and display them through MapLibre with cached trip-area tiles where allowed. Parse forwarded reservation text locally into editable fields without logging message content. Build a day timeline, route overview, conflict warnings, timezone display, and offline printable itinerary. Allow manual updates for delays and reservations and label all external data with source and timestamp. Export a complete trip bundle as JSON, calendar file, Markdown, and PDF. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure. Deliberately leave out live flight, hotel, award, or ticket inventory. Deliberately leave out commercial turn-by-turn navigation and global offline maps. Deliberately leave out booking guarantees, disruption rebooking, and traveler support. Finish by running the tests and listing the exact commands used. ## Required capabilities - modern browser - MapTiler or compatible map key - user-entered reservations - optional public transit or weather API ## 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 production product version of Point.me. 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 ===== # Point.me product brief ## Problem A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Point.me, store manually researched award options and compare user-entered points values. The hard boundary is live award inventory search, airline program integrations, data operations, and concierge expertise, plus proprietary live data and network coverage. ## Product outcome Store manually researched award options, compare user-entered points values, map places and reservations, and keep an offline itinerary without claiming live proprietary availability. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - modern browser - MapTiler or compatible map key - user-entered reservations - optional public transit or weather API ## Explicit non-goals for v1 - live award inventory search, airline program integrations, data operations, and concierge expertise - live fare and inventory data - global routing dataset - crowdsourced trail intelligence - booking, disruption support, and offline map fleet ## 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 a closest honest personal substitute for Point.me in an empty repository. Use Next.js 15, TypeScript, SQLite, MapLibre GL, and user-supplied map and travel APIs; do not offer alternative stacks. The core loop is: store manually researched award options, compare user-entered points values, map places and reservations, and keep an offline itinerary without claiming live proprietary availability. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create trips, days, places, reservations, notes, documents, packing items, and emergency contacts. Geocode only user-entered places and display them through MapLibre with cached trip-area tiles where allowed. Parse forwarded reservation text locally into editable fields without logging message content. Build a day timeline, route overview, conflict warnings, timezone display, and offline printable itinerary. Allow manual updates for delays and reservations and label all external data with source and timestamp. Export a complete trip bundle as JSON, calendar file, Markdown, and PDF. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure. Deliberately leave out live flight, hotel, award, or ticket inventory. Deliberately leave out commercial turn-by-turn navigation and global offline maps. Deliberately leave out booking guarantees, disruption rebooking, and traveler support. Finish by running the tests and listing the exact commands used. ## 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 Point.me capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Point.me indie build ## Goal Build the smallest trustworthy replacement for the core Point.me workflow for one developer or a tiny team. ## Scope Store manually researched award options, compare user-entered points values, map places and reservations, and keep an offline itinerary without claiming live proprietary availability. ## 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: - live award inventory search, airline program integrations, data operations, and concierge expertise - live fare and inventory data - global routing dataset - crowdsourced trail intelligence - booking, disruption support, and offline map fleet If those capabilities are essential, use Wanderer 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 a closest honest personal substitute for Point.me in an empty repository. Use Next.js 15, TypeScript, SQLite, MapLibre GL, and user-supplied map and travel APIs; do not offer alternative stacks. The core loop is: store manually researched award options, compare user-entered points values, map places and reservations, and keep an offline itinerary without claiming live proprietary availability. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create trips, days, places, reservations, notes, documents, packing items, and emergency contacts. Geocode only user-entered places and display them through MapLibre with cached trip-area tiles where allowed. Parse forwarded reservation text locally into editable fields without logging message content. Build a day timeline, route overview, conflict warnings, timezone display, and offline printable itinerary. Allow manual updates for delays and reservations and label all external data with source and timestamp. Export a complete trip bundle as JSON, calendar file, Markdown, and PDF. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure. Deliberately leave out live flight, hotel, award, or ticket inventory. Deliberately leave out commercial turn-by-turn navigation and global offline maps. Deliberately leave out booking guarantees, disruption rebooking, and traveler support. Finish by running the tests and listing the exact commands used. ## Required capabilities - modern browser - MapTiler or compatible map key - user-entered reservations - optional public transit or weather API ## 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.
PRODUCT.md
# Point.me product brief ## Problem A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Point.me, store manually researched award options and compare user-entered points values. The hard boundary is live award inventory search, airline program integrations, data operations, and concierge expertise, plus proprietary live data and network coverage. ## Product outcome Store manually researched award options, compare user-entered points values, map places and reservations, and keep an offline itinerary without claiming live proprietary availability. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - modern browser - MapTiler or compatible map key - user-entered reservations - optional public transit or weather API ## Explicit non-goals for v1 - live award inventory search, airline program integrations, data operations, and concierge expertise - live fare and inventory data - global routing dataset - crowdsourced trail intelligence - booking, disruption support, and offline map fleet ## 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 a closest honest personal substitute for Point.me in an empty repository. Use Next.js 15, TypeScript, SQLite, MapLibre GL, and user-supplied map and travel APIs; do not offer alternative stacks. The core loop is: store manually researched award options, compare user-entered points values, map places and reservations, and keep an offline itinerary without claiming live proprietary availability. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create trips, days, places, reservations, notes, documents, packing items, and emergency contacts. Geocode only user-entered places and display them through MapLibre with cached trip-area tiles where allowed. Parse forwarded reservation text locally into editable fields without logging message content. Build a day timeline, route overview, conflict warnings, timezone display, and offline printable itinerary. Allow manual updates for delays and reservations and label all external data with source and timestamp. Export a complete trip bundle as JSON, calendar file, Markdown, and PDF. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure. Deliberately leave out live flight, hotel, award, or ticket inventory. Deliberately leave out commercial turn-by-turn navigation and global offline maps. Deliberately leave out booking guarantees, disruption rebooking, and traveler support. Finish by running the tests and listing the exact commands used. ## 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 Point.me 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 · this prompt is generated from the build plan · improve it via PR
People still pay for Point.me because travel subscriptions sell current data and confidence during disruption, not just an itinerary list. The recurring cost buys map licensing, fare feeds, reservation access, route freshness, disruptions, geocoding, caching, offline data, and support, not just the visible interface.
xlive award inventory search, airline program integrations, data operations, and concierge expertise
xlive fare and inventory data
xglobal routing dataset
xcrowdsourced trail intelligence
xbooking, disruption support, and offline map fleet
share on X ↗"I just replaced Point.me ($10.75/mo) with one prompt"
Point.me pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| basic | $0/user | $0/user | Explore browsing only; 0 live award searches, 0 route alerts, and 0 included concierge work |
| standard | $12/user | $10.75/user | Unlimited 365-day award searches subject to fair use; 3 active route alerts |
| premium | — | $21.67/user | 5 active route alerts, $100 concierge credit, 10% concierge discount, and 1 strategy consultation valued at $200 |
| concierge | custom | — | Hands-on award-booking service for 1 passenger |
free tierBasic plan: Explore only; 0 live searches, 0 route alerts, and 0 concierge credit.
billingStandard monthly or annual; Premium annual only; Concierge charged per passenger
hidden costsThe advertised unlimited Standard searches are subject to a fair-use policy. Concierge starts at $200 per passenger and can exceed the subscription price.
verified 2026-08-14 · source ↗
Vibecode Point.me
Not really. Point.me's value is not the code: Recheck price before merge. See the honest breakdown above.
How much does Point.me cost?
Point.me costs about $10.75/month (Standard, checked 2026-07-31), which is $129 per year.
What do I lose by replacing Point.me?
Honestly: live award inventory search, airline program integrations, data operations, and concierge expertise; live fare and inventory data; global routing dataset; crowdsourced trail intelligence; booking, disruption support, and offline map fleet. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Point.me?
Yes: Wanderer (Open-source self-hosted trail database and route explorer using open map data.). Using prior art is also vibecoding; the prompt is for when you want it exactly your way.