Height height.app

Can AI replace Height?

Height's solo core is compact: build a single-user AI project management workspace with projects, tasks, statuses, filters, recurring items, and JSON export. A competent builder can reach a useful personal version in one sitting, while the paid product mainly wins on collaboration, integrations, polish.

Verdict: Bot · AI can build you a working versionBuild time: one sittingDiscontinued
Bot

01What it costs

Price variesTypical paid plan, paid plan; billing basis requires review

Checked Jul 31, 2026 · source: height.app.

02Could AI build it for you?

The core job: Build a single-user AI project management workspace with projects, tasks, statuses, filters, recurring items, and JSON export.

What a working version needs:

  • Node.js 22
  • local or self-hosted runtime
  • SQLite database

Strong page because Height separates a compact personal workflow from the value of long-term polish.

03What you'd give up

  • enterprise permissions
  • large integration catalog
  • mobile capture and notifications
  • real-time multiplayer

Height: Teams paid because shared state, notifications, permissions, and migrations are harder than the visible board or list.

04Free and cheaper alternatives

YouTrackfree

Tasks, articles, no-code workflows, dashboards, and weekly AI credits for ten people

jetbrains.com →

05The build prompt

Paste this into an AI coding tool (such as Claude, ChatGPT, Lovable or Replit) to build your own version.

prompt.txt
Build a usable personal replacement for the core loop of Height.
Use exactly this stack: Next.js 15 + TypeScript + SQLite.
Primary job: Build a single-user AI project management workspace with projects, tasks, statuses, filters, recurring items, and JSON export.
Start from an empty folder and create the complete working project.
Make the default mode single-user and private.
Store user data locally unless the core job requires the declared self-hosted database.
Do not add analytics, telemetry, ads, or third-party accounts.
Put every secret and external credential in .env and provide .env.example.
Use realistic sample data that is clearly labelled and easy to delete.
Implement the smallest polished interface that completes the core loop end to end.
Include clear empty, loading, validation, success, and failure states.
Add import and export so the user is not trapped in the app.
Use accessible keyboard navigation, labels, focus states, and sensible contrast.
Validate untrusted input and never log secrets or private file contents.
Deliberately exclude these paid-product advantages: enterprise permissions; large integration catalog; mobile capture and notifications.
Do not fake integrations, network effects, proprietary data, model quality, compliance, or security claims.
Where an external API is optional, keep the app useful without it and explain the degraded mode.
Write focused unit tests for the data model and the most important workflow.
Add one end-to-end smoke test that proves the core loop works.
Create a README with setup, permissions, architecture, data location, backup, and limitations.
Add scripts for install, development, test, build, and a production-style local run.
Run the tests and build before finishing, then fix errors rather than merely describing them.

06Open-source starting points

  • Vikunja: Open-source task manager with lists, boards, and collaboration.
  • Plane: Open-source issue and project tracker.
Sponsor slot · openFeatured alternative to Height. A labeled card for one relevant tool.
Book this spot →

App prices, verdicts, alternatives and build prompts are adapted from Can I Vibecode It? (MIT License, © 2026 Rob Hallam). Each price shows the date it was checked and its source. Prices change; confirm on the vendor's site before you decide.