Skip to main content

What Appsterisk is

A brand today publishes a list: Instagram, X, YouTube, a website, a WhatsApp number, an address, a campaign link. Every one of those is a platform's address for you, and every one of them changes.

Appsterisk replaces the list with one identifier.

*jornalnacional

The identifier is not a page. It is a name you own that resolves to whatever you currently are — your contacts, your collections, whatever is relevant this week. The destinations change; the name does not.

Why that matters​

A QR code printed on a poster keeps working after you redesign your website. A name read aloud on television still resolves next year. You stop teaching people a platform's address for you and start teaching them yours.

That is the whole thesis: stop promoting platforms, promote yourself.

The four ideas​

Namespace. The name itself — *metallica. Owned, renewable, transferable. Some names are free, most are a fixed price, the short and generic ones cost more, and some are held back.

Identity. What the name resolves to: a display name, an avatar, a description, verification.

Contacts. Where you are — website, socials, phone, address. Marked public or private; private ones never leave your dashboard.

Collections. Groups of links that can carry a time window. *metallica during a São Paulo concert week leads with the São Paulo collection, and returns to the default afterwards without anyone editing anything.

What Appsterisk is not​

Not a website builder, not a CMS, not a social network, not a link-in-bio page with a nicer theme.

The distinction is real and shapes the product: the resolver is the primitive, and the rendered profile is one of its clients. The same manifest that draws the page is a documented, cacheable API that anything else can read.

It answers three questions and declines the rest:

  • Who is this identity?
  • Where is this identity present?
  • What is relevant right now?

Reading order​

  • Product — how namespaces, ownership, collections and resolution work.
  • Developers — running it locally, the API, the manifest format.
  • Operations — deploying, monitoring, rotating keys.
  • Policies — the rules, the threat model, and what is shared with Webhookr.

Documentation here marks what is enforced versus what is decided but unbuilt, and the policy pages count the difference. That is deliberate: a rule nobody enforces is a promise, not a control.