Aller au contenu
Bastide Connexion Créer un compte
Press / to search

Glossary

FrançaisMarkdownv0.3.0

The manual's terms, in alphabetical order, each defined in one sentence. The main objects and how they relate are explained at more length in Concepts.

TermDefinition
AccountA person's identity: an address, a password, their second factors and their tokens.
AgentA program, often an AI assistant, that operates Bastide over MCP on a person's behalf.
Agent tokenThe token issued to an MCP client after your consent on the Autoriser un client MCP (Authorise an MCP client) page.
AuthenticationThe service that signs up and signs in your application's users, provided with the backend.
BackendWhat comes with every project: PostgreSQL database, authentication, object storage and realtime.
Branch addressA branch's moving address, which always serves its latest deployed commit.
BuildThe step of a deployment that fetches the repository, installs dependencies and produces a signed image.
Build minutesBuild time counted each month, included according to the tier.
CheckA verification a release must pass before it is promoted to production.
Cross-cutting roleA role added on top of the rank: Security or Billing.
Database branchA copy of a project's database, to work on without touching production.
DeploymentThe request to put a version into an environment, from build to going live.
Deployment addressThe immutable address of one specific deployment, whose content never changes.
Deployment hookA signed address that, when called, deploys a branch to an environment.
EdgeThe network layer that receives traffic, terminates HTTPS, routes to your application and serves the cache.
EnvironmentA deployed instance of a project, with its variables: production, staging, preview or custom.
Environment variableA configuration value specific to an environment, possibly secret.
Exit archiveThe package holding a whole project in open formats, to restore it elsewhere.
FrameworkYour application's framework (Next.js, Astro, Nuxt…), detected in the repository.
Free projectA verified person's free-for-life project, with its own limits.
Idempotency keyA value attached to a write: replayed with the same key, the write returns the first response with no new effect.
MCPModel Context Protocol: the protocol through which an agent discovers and calls Bastide's tools.
MCP clientAn application that connects to Bastide's MCP server, such as Claude Code.
MCP toolAn operation exposed to an agent, named with underscores (deployment_create).
MemberAn account that holds a role in an organization, or on just one of its projects.
OperationA platform action, published in the registry, served identically by the API, the command line and MCP.
OrganizationA team's space: its members, its projects, its billing and its spending cap.
Outbound networkThe connections an application may open to the outside: closed, open or restricted.
PasskeyA second factor built into a device or held on a hardware key (WebAuthn standard).
Personal tokenA pat_… token that acts in a person's name, limited by scopes and an expiry.
PinningThe state of an environment frozen on a release, which new deployments do not replace.
PreviewAn environment attached to a branch, to review a change before merging it.
ProductionThe environment that serves your public site, created with the project.
Production branchThe Git branch whose pushes deploy to production; main by default.
ProjectThe unit of hosting and billing: one application, its environments and its backend.
PromotionPutting an already built release into service in an environment, without rebuilding.
Publishable keyThe backend key your application may expose to the browser; it only grants what the policies allow.
RankA role's place in the hierarchy: Reader, Developer, Maintainer, Administrator, Owner.
RealtimeThe backend's broadcast and presence service, enabled per project.
Recovery codeOne of the ten single-use codes that stand in for a lost second factor.
ReleaseThe built and signed image a successful deployment produces; it is what you promote or restore.
RestorePutting an environment's previous release back into service, without rebuilding.
Reversible actionAn operation classed by what it takes to undo it: N (read), R (reversible), E (approved by a person, undoable for five minutes), I (irreversible, two approvals and twenty-four hours of grace).
ScopeA named right of a token (deploy:write, secrets:write…), added on top of its holder's rank.
Second factorProof on top of the password: a code from an authenticator app, or a passkey.
Secret keyA server-only backend key, shown once when it is created.
Service accountA non-human identity whose tokens act under their own name, on named projects.
SessionA person's connection to the console: eight hours at most, one hour without activity.
Single sign-onSigning in to the console through the organization's OpenID Connect identity provider (SSO).
SleepStopping an environment after a period without requests; it wakes on the next visit.
Spending capThe monthly amount an organization cannot exceed; €500 at creation.
StagingAn environment that mirrors production, to validate before promoting.
Starter templateA ready-to-deploy repository written by Glowsoft, offered on Modèles de départ (Starter templates).
StorageThe backend's object service: buckets, files, signed URLs and image transformations.
TaskA long-running operation placed in a queue (job_…), whose progress task_read reads.
TierA project's level of resources and price: Discovery, Standard, Pro or Sovereign.
TokenWhat you present in the Authorization: Bearer header to call the API.
TrashThe state of a deleted project, for thirty days, from which it can be restored.
Unclaimed projectA project created by an agent, switched off after seven days unless a person claims it.
WebhookAn HTTP call Bastide sends to your address when an event occurs.

See also

Report a mistake on this page