Glossary

Glossary

The words the tutorials use, each with what it means on the Agentic Developer Hub and the tutorials that use it.

Overview

Search for a word, or read down the list. A term that a tutorial depends on is also shown in that tutorial's Definitions.

Terms

15 terms

Application

A piece of software that people reach your product through, such as a website or a mobile app. You register each one in your product's Applications, so the hub knows it and can send people back to it after they sign in. Applications is also the name of the feature that holds them.

Tutorials: Add sign-in and a /home page to a website

Client id

The name the hub gives an application when you create its login registration. Your website sends it with every sign-in, so the hub knows which product's sign-in page to show and where it may send the person back. It is not a secret.

Tutorials: Add sign-in and a /home page to a website

Ecosystem

A boundary around a set of data. Everything inside it belongs to it: its users, its storage, its settings and its applications. Nothing outside can reach in unless you let it.

Ecosystems nest. Your workspace has one, and each product you make is a new one inside it. An ecosystem's address is its parent's address with its own slug added to the end, so a product called notes in a workspace whose address is ecosystem.fishlamp lives at ecosystem.fishlamp.notes.

Tutorials: Create an ecosystem and add features, Add sign-in and a /home page to a website

Feature

One thing a product can do, such as keeping users, storing files or registering applications. You switch features on from one list that every product shares, and the hub sets up what each one needs, such as a place for its data. A few features belong only to a workspace, and the list shows them greyed out.

Features depend on each other in two ways:

  • Some features come with another. They are not listed on their own. Switching on Users brings Authentication and Email Signup with it, and removing Users removes them too.
  • Some features need another. Switching one on switches on everything it needs as well. Applications needs Users, Feature flags and Server bags, so adding Applications adds all of them. A feature that another one still needs cannot be removed until that one goes first.

Removing a feature turns it off and keeps its data.

Tutorials: Create an ecosystem and add features

Hosted sign-in

How a product's users sign in. Your website does not keep passwords. It sends the person to the hub's sign-in page for your product, where they sign in or create an account. The hub then sends them back to your site with a token, and your site keeps it.

Tutorials: Add sign-in and a /home page to a website

Invitation

A message that lets one person create an account in your product. You send it from Pending users, by email, text message or both. It lasts fourteen days, and the hub matches it by the email address it went to. Invitations are checked only when the sign-up mode is Invite only.

Tutorials: Add sign-in and a /home page to a website

OAuth provider

Another service a person can sign in with instead of an email address and a password, such as GitHub. A product's Authentication settings list the providers your hub offers, and you choose which ones its users may use.

Tutorials: Add sign-in and a /home page to a website

Personal and Organization ecosystems

The one ecosystem the hub makes for each workspace: a Personal ecosystem if the workspace is yours, or an Organization ecosystem if it belongs to an organization. It holds the workspace's own data, such as your notes, your storage and an organization's teams, and the hub sets up its features itself. The products you make sit beside it. The slugs personal and organization are kept for these two ecosystems, so a product can't use them.

Tutorials: Create an ecosystem and add features

Product

An ecosystem with a name, which you make in your workspace's Products. A new product starts empty: it has no users, no storage and no applications until you add the features that hold them.

Tutorials: Create an ecosystem and add features, Add sign-in and a /home page to a website

Redirect URI

An address on your website that the hub may send a person back to after they sign in, such as /callback on your site's own address. The hub sends people only to the addresses you list, so a stranger's site can't receive them.

Tutorials: Add sign-in and a /home page to a website

Sign-up mode

The setting that decides who may create an account in your product:

  • Open. Anyone who can sign in can create an account.
  • Invite only. Only people you have invited can create an account. A new product starts here.
  • Closed. Nobody new can create an account. People who already have one still sign in.

Tutorials: Add sign-in and a /home page to a website

Slug

The last part of an ecosystem's address, such as notes. It uses lowercase letters, digits and hyphens, and no two ecosystems in a workspace can share one.

Tutorials: Create an ecosystem and add features

Token

The proof of who a person is that the hub gives your website after they sign in. Your site keeps it, and asks the hub who it belongs to before it shows a signed-in page. When the hub refuses a token, the person signs in again.

Tutorials: Add sign-in and a /home page to a website

User

A person who uses your product. Your product's users belong to it alone, and the hub keeps them apart from you and from every other product. Users is also the name of the feature that holds them.

Tutorials: Create an ecosystem and add features, Add sign-in and a /home page to a website

Workspace

Where you work on the hub: your own, or an organization's. It has an ecosystem of its own, and every product you make is nested under it.

Tutorials: Create an ecosystem and add features

Links