Sign In As You

You have your own personal website or a profile on a platform you use a lot. With IndieAuth, you can use it as a means of signing in! No more extra passwords.

A Web resource that you own.

1. Setting Up

Fortress acts as an proxy between you and other sites. Currently, Fortress only supports sites that

It takes only four steps to get it out on a homebrew site; even less depending on how your site handles these options.

2. Adding Verified Links

There's two ways to add verified link support to your personal website: using a <link> tag or a <a> tag on your website's homepage. It'd look something like the following:

Code Example
<!DOCTYPE html> <html lang="en"> <head> <title>Jacky Alcine</title> <meta name="viewport" content="width=device-width, initial-scale=1"> <!-- Using an account on a silo --> <link rel="me" href="" /> <!-- Using an account on a federated platform --> <link rel="me" href="" /> </head> <body> <p> I use my <a href="" rel="me">Mastodon</a> account more than my <a href="" rel="me">Twitter</a> account. </p> <aside class="h-card"> <a href="/" rel="me" class="u-url"> <img class="u-photo" src="" /> <span class="p-name">Jane F. Doe</span> </a> <p class="p-note"> In 1968, I became the first black woman elected to the United States Congress. In 1972, I also became the first black candidate for a major party's nomination for President of the United States, and the first woman to run for the Democratic Party's presidential nomination. </p> </aside> </body> </html>

3. Hooking Up Your Site

With your verified links in place, Fortress can be presented as your sign-in option. Adding a few more lines of HTML to your site (or however your site handles authentication endpoints as well as token endpoints ) is all you'd have left to do!

Code Example
<!DOCTYPE html> <html lang="en"> <head> <title>Jacky Alcine</title> <meta name="viewport" content="width=device-width, initial-scale=1"> ... <link rel="authorization_endpoint" href="" /> <link rel="token_endpoint" href="" /> </head> <body> ... </body> </html>

4. Testing it Out

Doing the above will be enough to have your site fully IndieAuth compatible and powered by Fortress (and the providers you've set up)! Try it out by using the demo after you're done.


Designed For People, Not Machines

This approach for authentication lets you portably move from relying on a company to provide your data and identity to you defining it on your own terms; exposing the bits of data that you choose to provide.


Sites that support IndieAuth as a means of logging in never need to know how you signed in and you never need to expose more information than you have to when authenticating yourself.


Fortress works with silos and federated services by allowing you to verify your identity with them and use them as a means of identifying yourself to a Website.

Plug and Play

It's a fast way for application developers to get up and running with supporting IndieWeb-capable identities. Your site becomes your source of truth and identity on the Web.

Easy to Remember

No more stressing over what password, username or e-mail you've used for a particular site — Fortress abstracts that away for developers and lets the user define how they'll identity themselves.

Try it Out

Sign in using your URL to access a dashboard specifically for your site held here on Fortress.

A Web resource that you own.