Use Nebla

Projects and access

Everything you create in Nebla, such as servers, volumes, firewalls, SSH keys and API tokens, belongs to a project. People see only the projects they are members of.

Projects

Any user can create a project and becomes its owner. A non-admin user can own up to 3 projects unless the panel admin changes PANEL_MAX_PROJECTS_PER_USER. Projects a non-admin creates get the panel's default quota. Projects a panel admin creates have no limits.

Switch projects from the project menu in the top bar. Press ⌘ K on a Mac, or Ctrl K elsewhere, to search pages, servers and SSH keys.

Under Settings in a project:

  • Owners and admins can rename the project.
  • Any member can leave it. The only owner can't leave until someone else is an owner too.
  • An owner can delete the project by typing its name. Delete its servers and volumes first.

Roles

RoleCan do
OwnerEverything, including deleting the project and adding or removing other owners.
AdminEverything except deleting the project or changing owners. Manages members, invites and API tokens.
MemberCreates, changes and deletes servers, volumes, firewalls and SSH keys.
Read-onlySees everything in the project and changes nothing.

A project always keeps at least one owner. When someone is demoted below admin or removed, their API tokens and pending invites are revoked.

Invites

On Members, choose Invite, enter an email address and pick a role. The invite link is shown once, so copy it. If the panel has SMTP set up, Nebla also emails it.

  • Links expire after 7 days. Pending invites lists them, with a Revoke button.
  • The person accepting must be signed in with the invited email address.
  • Someone without an account can create one from the invite when open sign-up is on, or when a panel admin sent the invite.

SSH keys

On SSH keys, choose Add SSH key and paste one public key line. Ed25519, RSA, ECDSA and security-key (sk-) keys are accepted. The name defaults to the key's comment. Each key and name is unique within a project.

Pick keys when you create a server. Cloud-init installs them for the image's default user.

API tokens

Owners and admins manage tokens on API tokens. A token belongs to one project and is either Read or Read and write.

  • The token starts with nb_ and is shown once, when you create it. Nebla stores only a hash.
  • Tokens don't expire. Revoke one and anything using it stops working straight away.
  • The list shows when each token was last used.
  • A token reaches only that project's resources: servers, volumes, firewalls, SSH keys, actions, and the locations, images and server types the project can use.

Use a token with the CLI or the API. Requests are limited to 3600 an hour per token, with bursts of up to 100.

Your account

Account settings holds your name, your password and your sign-in methods. Your email address can't be changed there.

  • Password. At least 10 characters. Changing it signs out your other sessions.
  • Two-factor login. Turn on TOTP with your password, an authenticator app and a 6-digit code. Turning it off needs a code and your password.
  • Passkeys. Add up to 10. Signing in with a passkey skips the two-factor code. Passkeys need the panel on https with a domain name. Removing one signs out your other devices.

If you lose your second factor, a panel admin can reset two-factor login and remove passkeys from your account.