Silicon Accounts · Start

Follow a guide to complete a task, with the commands to run and the results to expect.

Add sign-in to your appSend your users to us to sign in, bring them back to your app, and exchange the code they return with for their tokens.
Sign in with the hosted pagesSend your users to our sign-in pages and bring them back to your app. Set up the callback, check the state and exchange the code on your server.
Embed the sign-in buttons in an iframePut your app's sign-in buttons on your own page in an iframe. Allow your site's origin, add the frame and handle the return like any other sign-in.
Drop in the SDK snippetAdd one script tag and your sign-in buttons show up on your page. Set up the buttons, then finish the sign-in through your server's callback.
Use any OpenID Connect libraryPoint any OpenID Connect library at us. Give it your app's credentials, run the sign-in and read the verified account details.
Exchange, refresh, check and revoke tokensTurn a sign-in into tokens, keep the session going, check who a token belongs to and end it when the account signs out.
Configure sign-inChoose how Carbons sign in to your app, what they share with you and where they come back to. Every change gets a version and lands in the history.
Brand the sign-in pagesMake the sign-in pages, the iframe and the buttons look like your app, with your colours, fonts, logo and layout.
Import existing usersBring the users you already have into Silicon Accounts from a CSV or JSON file. Dry run it first, import it, then fix the rows that failed.
Get a Silicon accountCreate your own Silicon account and name your Carbon as its custodian, or let your Carbon create it for you. Save the STK the moment you see it, and wait for approval if you need to.
Sign a Silicon into an appAs a Silicon, sign into any app with a short-lived token. You keep your STK to yourself, and the app exchanges the token for its own session.
Be a Silicon's custodianLook after the Silicons you're responsible for. Accept their requests, create them, change their details, rotate their STKs, or hand them over to another Carbon.
Use the silicon-accounts CLIInstall the silicon-accounts CLI, sign in, and drive it from your terminal or your scripts. See where it keeps your session and how to read its errors.
Run a Silicon in CI and the cloud with no stored secretLet a CI job sign in as your Silicon with the OIDC token its CI already gives it, and let the Silicon prove itself to AWS, Google Cloud and Microsoft Entra. No STK, key or cloud secret is stored anywhere.
Verify a proofWhen another app sends yours an App verification or User verification proof, ask us to check it, then read the answer and decide whether to allow the call.
Act for an account at another app (User verification)When your app needs to do something at another app for one of its users, get their agreement, ask us for a User verification proof and send it with your call.
Prove your app to other apps (App verification)Show another app that a call really comes from your app. You get one App verification proof for each app you talk to.
Receive webhooksWe tell your webhook when one of your users changes their account. Check each delivery's signature, answer fast and apply each event once.