Create your account

Sign up

Then connect an environment — scopes is what you are granting when you do. Organizations and teams is how more than one person gets in, and plans and pricing is what it costs.

Passwordless. A magic link or an emailed one-time code — six digits, five minutes, single-use.

There is no password, here or in the kit. The dashboard is a Pithy application composing the same auth capability you would.

Google and GitHub sign you in. They do not sign you up. A GitHub sign-in whose primary address matches no account here is refused, and nothing is minted — it used to create a second, empty user at that address and leave the real account untouched, which is a person locked out of their own organization by a setting on another website. Google keeps sign-up, and the asymmetry is about intent rather than trust: Google shows an account picker, so the address somebody arrives with is the one they chose for this sign-in, while GitHub hands over whatever the primary happens to be. A refused provider sign-in returns to the control that started it and says so, rather than landing on a page that says nothing.

A provider can be attached afterwards, from your profile. That is the only way GitHub ever works for you, since it mints no account: sign in by link once, then connect the identity to the account you already have. Disconnecting one always leaves the sign-in link, which always reaches your address, so there is no this cannot be removed to run into. What does refuse both presses is freshness — attaching or removing a provider needs a recent sign-in, and a session older than that is refused rather than asked twice.

No address is matched between them. What is proved is control of the provider identity, so a GitHub primary of jim@personal.example attaches to an account signed in as jim@pithy.sh. The row that results shows the provider and nothing else: no address, no account id, no issuer.

An account on its own shows nothing

Because there is nothing to show.

The dashboard holds no copy of your data. Until you connect an environment, there is no Worker to read from — and connecting is a deliberate act you perform from your own machine.

Signing in with nothing waiting used to be a dead end. It said you belong to no account — ask somebody who is to add you, to somebody with nobody to ask, so the first person in any environment could sign in and reach nothing at all. There is a screen now: one field, and it is the name.

  • The slug is generated and never shown. No URL here contains one and nothing renders one, and it has to be unique — so a chosen one would mean collision errors and a message that leaks which names are taken.
  • A collision is never disclosed. A taken slug is retried with the next one, silently, so two teams at one company both get an account called Acme and neither learns of the other. An account named Acme already exists would tell a stranger who our customers are.
  • The name is pre-filled from your email domain when the domain says something about a company, and left blank for a mailbox provider or a throwaway address. A suggestion says nothing about who owns a domain and grants nothing: no account is ever joined by domain. A second person from the same company with no invitation gets their own.
  • An invitation is named rather than acted on. The token is the invitation and this application holds only its digest — deliberately, so a read of that table cannot yield something redeemable. So the screen says the link in the mail is what joins you, and offers to make an account beside it rather than choosing for you.

Connect an environment

pithy dashboard connect --env prod

A device-code flow: a short code, your browser opens, you approve, the CLI receives a short-lived connect token.

Then the CLI writes the registration into your D1 — the one key it ever writes there.

Nothing reports connected until a signed ping round-trip succeeds against your Worker.

What you choose at connect

The scopes. That list is what you consent to, and it is written down rather than left to be read off a manifest.

The environment. One connection per project and environment — a staging credential cannot reach production, and the check is on the token.

What it resolves for you

The address. From your Worker’s domains declaration, else its first route pattern, else a hand-set base URL. It prints what it found and where it came from before registering.

--worker-url overrides, for a proxy whose address no config knows.

The Worker. In a project with several, connect refuses the ambiguity and asks for --worker <name> rather than guessing — and a Worker composing no control plane is refused outright, because there is nothing to connect to.

Free covers reading

The full audit trail. Every user, purchase and entitlement, readable. No time limit.

Acting on production from a browser is the paid part — see plans and pricing.

Connecting more than one project

A customer may register several, each with its own connection and keypair. The dashboard offers a picker when there is more than one.

A single project needs no ceremony.

What happens when your address changes

A custom domain, a renamed Worker, a moved environment breaks the connection.

pithy dashboard connect --update

A connection whose ping fails surfaces as needs reconnecting, never as a silent dead link.

ESC