deniz.in

Markets

Weather

Loading weather

· via dev.to (home feed)

Castly.sh launches developer push service with per-project VAPID keys and exportable subscribers

Castly, a new web push service announced on dev.to, gives each project its own VAPID keys and exportable subscriber data, taking aim at the lock-in that keeps push audiences tied to one vendor.

Castly.sh launches developer push service with per-project VAPID keys and exportable subscribers

A push service built around owning your subscribers

A developer has launched Castly, a web push notification service pitched at teams that want to keep control of their subscriber base. In a launch post on dev.to, the builder describes a familiar trap: on most push platforms, the audience a product accumulates effectively belongs to the provider, because leaving the service means leaving the subscribers behind.

Castly's answer is structural. According to the announcement, every project gets its own VAPID key pair — the cryptographic identity a server uses to send web pushes — and both the keys and the subscriber records can be exported. A developer who decides to leave can take the keys and the subscriber list along and keep the setup running elsewhere.

What the announcement covers

The post describes a deliberately small feature set. Integrating the service takes one script and a single API call to send a push, and the client SDK is under 3 KB. The free tier covers up to 10,000 pushes per month.

Beyond that, the announcement is thin: it does not detail paid plans, infrastructure, or delivery guarantees, and it showed no comments at the time it was fetched. This is a first-person launch note from the project's own developer, not an independent review.

Why VAPID keys are the lock-in point

Some background explains why key ownership is the crux. Web push in browsers rests on the Push API and the Web Push protocol: a user grants a site permission, the browser registers the subscription with a push service run by the browser vendor, and the site's server later sends messages through that service.

VAPID — Voluntary Application Server Identification — is how the sending server proves who it is, using a public-private key pair. The catch is that browsers associate a push subscription with the application server key that was used when the user subscribed. Change the key, and the existing subscriptions no longer match; in practice the site has to ask users to opt in again.

That is the lever push vendors typically sit on. When a provider generates the VAPID keys on a customer's behalf and stores the subscriber endpoints in its own database, those subscriptions cannot simply be repointed at another service. Migration turns into a re-permission campaign, and permission prompts are friction — there is no guarantee a user will grant the same consent twice. Castly's design, with developer-held per-project keys and exportable subscriber data, targets both halves of that dependency.

Why it matters

For a product that talks to its users through the browser — update feeds, changelog notifications, transactional alerts — the subscriber list is the asset. An arrangement where that asset evaporates on departure gives the vendor lasting pricing leverage and makes switching feel like starting from zero.

Castly itself is early-stage, announced in a single post, and the questions that usually separate a durable service from a launch demo — reliability at scale, what happens past the free allowance, long-term maintenance — are all still open. But the underlying bet is a sound one to watch: by handing developers the keys, literally, it treats push infrastructure as a replaceable utility rather than a one-way commitment.

  • #web-push
  • #developer-tools
  • #notifications
  • #vendor-lock-in
  • #saas

Related posts