Create a local world.
Run pricklypair init. The worker stores its policy, invitations and public checkpoint keys in your own local database.
PUBLIC STATE / PRIVATE AUTHORITY / 001
Give anyone a temporary link to attach a FIDO key, iPhone passkey, or dice-derived checkpoint. Delegate bounded access to autonomous agents. Compose institution-grade permission rules. Your own worker keeps the authorization state. No accounts, no signup, no centrally hosted customer secrets.
Individuals, agents, teams and institutions. Every feature in one plan. Preview available now. Subscribe, $7 a month.
curl -fsSL https://colony.technology/pricklypair/install.sh | shVersion 0.2.1 · pinned package SHA-256 · no sudo · installs under your own account. Inspect the installer before running it.
Run pricklypair init. The worker stores its policy, invitations and public checkpoint keys in your own local database.
Run pricklypair worker. For remote devices, give it your HTTPS origin and proxy traffic to the locally running port.
Use pricklypair invite. The recipient chooses FIDO, iPhone passkey, or dice on the temporary page. The invite expires after one claim and needs your local approval.
Run pricklypair request --effect '{"operation":"login"}'. The link conveys the operation; valid checkpoints satisfy the policy.
Create an agent key, request checkpoint approval once, and issue a bounded grant. Its own key signs every later request.
Combine allowed operations, audiences, resource prefixes, environment claims, amounts and time windows with finite policy expressions.
Scope of the developer preview. The local worker implements WebAuthn enrollment and assertion validation, dice-derived Ed25519 proofs, session-bound approval, multi-checkpoint policies, and agent key-bound delegation with condition and usage limits. A browser or terminal may request authority. The authorizing factors remain under the device owner's control.
Real FIDO and iPhone hardware acceptance, adversarial relay protection, independent audit, password vault/autofill, third-party login adapters, credential brokering and production transaction signing remain engineering gates. A one-time enrollment invitation grants the ability to request a new checkpoint and should be shared with the intended recipient. Publication of the separate public state coordinate grants no signing permission.
Operational boundary. colony.technology serves this download and documentation. Customer enrollment, factor records and approval sessions run on the operator's worker, with its own HTTPS address. The website does not store them.