Should you build your own Amie?
Combine calendar, tasks, contacts, and scheduling in a polished daily interface
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.
ENOriginal research content in English. Original prompt preserved in English.
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.The prompt opens pre-filled in your agent. Review it before running. · this prompt is generated from the build plan · improve it via PR
What would building your own look like?
Read one calendar, combine tasks and contacts in a daily view, publish availability, create conflict-safe bookings, and send confirmations and reminders.
What you will need
- Google Calendar OAuth credentials
- PostgreSQL
- public deploy target
- Resend API key
- domain with HTTPS
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.
xnative polish, sync, calendar providers, mobile apps, and integrated communications
xmultiple calendar providers
xteam routing and round-robin
xpayments
xtimezone edge-case maturity
How much does Amie cost?
- Monthly billing
- $28.84/mo$28.84/mo · per person
- Per year
- $346/yr$346/yr
- Annual billing
- $277/yr20% cheaper than paying monthly
- On a Brazilian card, with 3.5% IOF
- R$151/moR$1,447/yr
Saved to My list. You will see a notice on this site when the price changes.
You complete the purchase on Amie’s site. Vibe Radar does not handle payments.
| Plan | Monthly | Annual (per month) | What is included |
|---|---|---|---|
| free | $0/user | $0/user | 25 meeting-note credits one time; unlimited Google/Apple calendar connections and to-do lists; basic AI |
| pro | $28.84/user≈ $28.84 | $23.07/user≈ $23.07 | Unlimited meeting notes, bot-free recording, chat with notes and AI scheduling |
| business | $57.67/user≈ $57.67 | $46.14/user≈ $46.14 | Pro features plus custom templates/branding and ATS/CRM integrations |
| enterprise | custom | - | Custom security, support, deployment and enterprise controls |
Free tier25 meeting-note credits one time, unlimited Google/Apple calendars and to-do lists, and basic AI
Billing termsmonthly + annual (-20%); 7-day paid trial; subscriptions auto-renew
Additional costsTeam subscriptions are per seat and mid-cycle additions are prorated. VAT/taxes may be added, standard purchases are generally non-refundable, and USD cost moves with EUR/USD. Free meeting-note credits do not renew.
verified 2026-08-14 · source ↗
Is it cheaper to build or buy Amie?
Adjust the numbers: hours to build, your hourly rate, running costs and the subscription price.
Over 24 months, subscribing is cheaper.
Starting hours estimated from the analysis (multi-day). Does not price what you give up (support, integrations, security).
Can I rebuild Amie?
Kinda. The core of Amie is buildable in a weekend with the prompt on this page, but there are real gaps: native polish, sync, calendar providers, mobile apps, and integrated communications, multiple calendar providers. Read the honest list above before committing.
How much does Amie cost?
Amie costs about $28.84/mo (Pro, checked 08/14/2026), which is $277 per year.
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?
Yes: Cal.com (Mature open-source scheduling platform with calendar integrations and booking workflows.). Using prior art is also vibecoding; the prompt is for when you want it exactly your way.