Harkly mark

Customersask.Youbuild.Theyhearback.

Platform
Web · Self-host · In-app SDKs
Status
In development · beta list open
Scope
Platform, dashboard, SDKs, brand
harkly.app
Harkly — Customers ask. You build. They hear back.

The problem

Feedback tools charge by the seat, meter the AI by the resolution, and keep your customers' voices in someone else's cloud. Growing a team means growing the bill.

The idea

Price on identified customers, not headcount. Ship the whole loop in one flat-priced box — and let teams run that box on their own metal.

One request, start to finish, without anyone chasing it.

01

They ask

A board, a widget, the messenger, a survey, an email. Every request lands tied to the person and what they pay.

02

You decide

Votes weighted by revenue, segments over any attribute, a moderation queue, and a roadmap that only shows what you put on it.

03

You build

Post to Linear, GitHub or Jira in one click. When the issue closes, the post moves.

04

They hear back

Publish an update: every voter gets one email, the post flips to Completed, the widget shows the badge.

Everything Featurebase ships. Nothing it forgot.

Boards that rank themselves

Voting with duplicate suggestions while typing and merges that carry votes and comments over — weighted by the revenue behind them.

Roadmap, minus the theater

Column or timeline, public, private or segment-restricted. Only what you place on it is visible; the engineering backlog stays yours.

Changelog that closes the loop

Publish an update and every voter gets one email. Linked posts flip to Completed; the widget badge clears itself.

Support that knows who’s asking

Messenger, email and Slack in one thread, with plan and MRR attached. Copilot drafts are grounded in your help center only.

Trust, built in

Vote integrity, a moderation queue, PII scrubbing, an audit log, and per-user export and delete. Not bolted on.

Your stack, your data

One-click import from Canny, Featurebase and Intercom; full export any time. Run it at harkly.app or in one container of your own.

Zinc and ink, one signal blue.

The brand stays quiet — zinc surfaces, near-black type — so the blue lands where it matters: the ask, the vote, the reply. TWK Everett carries the headlines; IBM Plex Mono handles the code.

Harkly mark

The mark is a periwinkle dot inside a dark square — someone, listening.

Paper#FAFAFA
Zinc#F4F4F5
Signal#2A5F9E
Periwinkle#7FA3FF
Ink#18181B

Under the hood

A Turborepo of small services and SDKs — and a self-host story that fits the whole thing in one container.

Edge

  • Bun + Hono gateway
  • Redis-backed rate limits
  • Strips spoofable client headers

Core

  • Private Bun + Hono API
  • Drizzle ORM over Postgres
  • Email-code auth, no passwords

Data

  • Postgres + pgvector
  • Graphile Worker on the same DB
  • Event bus + full audit log

Surface

  • Next.js dashboard, three-column shell
  • React Email templates
  • Shared tokens across web and Swift

SDKs

  • @harkly/js — size-budgeted browser SDK
  • React wrapper + native Swift SDK
  • REST, webhooks, CLI, MCP server

AI

  • Grounded-only answers — no invention
  • Bring your own key: OpenAI, Anthropic, Gateway
  • Credits at cost, zero markup

In the wild

harkly.app
Harkly — the loop, the inbox, and support that knows who's asking
Visit harkly.appFree for 250 customers — then $39 a month for the whole team

Your customers are already asking.

We build products people can talk back to.