Replace Amie?

KINDA · weekend project
catalog price reference $15/mocategory 📅 schedulingreported replacement votes 0

The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Amie, combine calendar, tasks, contacts, and scheduling in a polished daily interface. The hard boundary is native polish, sync, calendar providers, mobile apps, and integrated communications, plus calendar integrations and reliability.

the prompt
Build a personal replacement for Amie in an empty repository.
Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, Google Calendar OAuth, and Resend; do not offer alternative stacks.
The core loop is: read one calendar, combine tasks and contacts in a daily view, publish availability, create conflict-safe bookings, and send confirmations and reminders.
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.
Implement one account with configurable working hours, buffers, minimum notice, and booking horizon.
Connect Google Calendar using OAuth and store refresh tokens encrypted at rest.
Calculate availability in UTC and render it in the visitor's detected timezone.
Reserve slots transactionally, create calendar events, and prevent concurrent double booking.
Send confirmation, cancellation, and reminder email with signed management links.
Add an admin booking list, event-type editor, audit log, and calendar reconnect flow.
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.
Deliberately leave out Microsoft and Apple calendar support.
Deliberately leave out team round-robin routing.
Deliberately leave out payments, CRM workflows, and enterprise controls.
Finish by running the tests and listing the exact commands used.

$ open in your agent (prompt prefilled, you press enter) or copy it raw · this prompt is generated from the build plan · improve it via PR

why people still pay

People still pay for Amie because people pay because one double booking or missed invite can cost more than years of subscription fees. The recurring cost buys OAuth refresh, webhooks, timezone databases, race conditions, reminders, deliverability, privacy, and uptime, not just the visible interface.

what you lose

xnative polish, sync, calendar providers, mobile apps, and integrated communications

xmultiple calendar providers

xteam routing and round-robin

xpayments

xtimezone edge-case maturity

prior art to inspect before buildingCal.comMature open-source scheduling platform with calendar integrations and booking workflows.
reported replacements · 0share on X ↗"Amie replacement research and build prompt"
questions
What does the Amie verdict mean?

The core job looks buildable, with meaningful gaps: native polish, sync, calendar providers, mobile apps, and integrated communications, multiple calendar providers. Read the full tradeoff list before committing. This research record is not a hosted IVCIFY tool.

What price does this directory record show for Amie?

The directory records $15/month for Pro, checked 2026-07-31. Verify the source before making a purchase decision. This reference stays outside retail Stack Math unless current matched evidence supports the comparison.

What do I lose by replacing Amie?

Honestly: native polish, sync, calendar providers, mobile apps, and integrated communications; multiple calendar providers; team routing and round-robin; payments; timezone edge-case maturity. If any of those are load-bearing for you, keep paying.

Is there an open-source alternative to Amie?

The listed prior art includes Cal.com (Mature open-source scheduling platform with calendar integrations and booking workflows.). Inspect those projects before starting from a blank prompt.