Onboarding

Your journey with Nebula starts with your onboarding! Learn how you can create your account, invite team members to your workspace, and manage different aspects like projects, permissions, and billing for your team.

Setting up your Nebula account only takes a couple of steps:

Nebula onboarding flow

You can sign up using your Google or Github accounts, or with an email and password pair.

When you sign up using an email and password pair, you have to verify your email address. Nebula sends a one-time passcode to the email you provided - use that passcode to verify your email address.

The Console then guides you through these steps:

Add your contact details
Set up your first project
Confirm your billing details

You're done! You can now access the Console and start using Nebula’s services to build, deploy, and scale your projects.

Create resources

You can start creating server and storage instances as soon as you access the Console. However, we recommend that you first define and set up your project structure and invite your team members.

Check out the relevant guides for NebCompute and NebStore.

Migrate to Nebula

Thinking about moving your applications, code, or files from a different cloud provider to Nebula?

Migration guides are available for both server provisioning and cloud storage.

Check out the migration guides for NebCompute and NebStore.

Set up your team

Once you access your Console, you can start setting up your team in the Access manager. Invite team members by adding their email addresses, and selecting:

the initial project they get access to
the user role they receive

You can invite multiple users at the same time. You can also add the same user to multiple projects at the same time: simply add their email address again and select a different project.

Roles and permissions

Nebula offers full Identity and Access Management through the Nebula Console. This gives you control over who can access your resources, and what actions they can perform. The Console’s Access manager serves as the central hub for managing user identities, authentication, and authorization across your entire infrastructure. The Console enables you to:

Select appropriate user roles for every user in your organization, with granular permission levels for accessing and managing your resources.
Audit user activity through detailed logging about every user action on every resource.

All team members that you invite receive a user role with a set of permissions. These permissions define how members of your team can manage user access, handle projects and resources, manage costs and billing, and access activity logs or reports.

The available roles are:

Owner
Admin
Project Lead
Developer
Finance Manager
Viewer

Unsure about which roles would be useful for your team?

Separating Admin and Developer roles is typically enough for teams that use a flat organization structure. All other roles are available for use cases when you need more fine-grained control over permissions, for example with larger or distributed teams.

Get in touch with our Support team if you need more details!

Open this toggle to view a detailed matrix of permissions tied to each available user role.

	Owner	Admin	Project Lead	Developer	Finance Manager	Viewer
Access Management
View access manager	✅	✅	✅	❌	❌	❌
View member	✅	✅	✅	❌	❌	✅
Invite member	✅	✅	✅	❌	❌	❌
Assign roles and permissions	✅	✅	❌	❌	❌	❌
Delete member	✅	❌	❌	❌	❌	❌
Resource Management
Create Resource	✅	✅	✅	❌	❌	❌
View Resources	✅	✅	✅	✅	✅	✅
Edit Resource	✅	✅	✅	❌	❌	❌
Delete Resource	✅	✅	❌	❌	❌	❌
Project Management
Create projects	✅	✅	✅	❌	❌	❌
View projects	✅	✅	✅	✅	✅	✅
Edit project	✅	✅	✅	❌	❌	❌
Invite member to project	✅	✅	✅	❌	❌	❌
Remove member from project	✅	✅	✅	❌	❌	❌
Delete project	✅	✅	✅	❌	❌	❌
Billing and Cost
View Billing Information	✅	✅	✅	❌	✅	❌
Edit Billing Information	✅	✅	❌	❌	✅	❌
View Cost summary	✅	✅	❌	❌	✅	❌
Delete Billing Information	✅	✅	❌	❌	✅	❌
Organization Settings
View settings	✅	✅	✅	✅	✅	✅
Update settings	✅	✅	❌	❌	❌	❌
Monitoring and Reports
View activity logs	✅	✅	✅	✅	✅	✅
Download activity logs	✅	✅	✅	✅	✅	❌
Delete activity logs	✅	❌	❌	❌	❌	❌
Manage API keys
Renew API key in a project	✅	✅	❌	✅	❌	❌

Set up projects

Nebula’s services are structured around projects.

Your first project, along with your team’s organization is automatically created during your sign-up process. Here’s how Nebula structures your projects:

Organization and project structure diagram

Your organization contains your projects and the users in your team.
You can create multiple projects within your organization, with team members having different roles for each project.
Each project in your organization can run separate server and storage instances.

When you log into the console, you always have a currently active project. The Console shows server and storage instances only for the currently active project. You can switch projects on the Projects page or through the Projects dropdown menu in the top left.

Visit the Projects page in the Console to create a new project.

Nebula enables you to create additional projects without any extra fees. Using multiple projects can enable you to create a work environment where you have:

separate projects for servers running development, testing, and production environments
multiple projects for product variants, or different regions for your applications
create standalone projects for different departments within your team to enable accurate and traceable billing

Manage projects and team members

You can manage projects within your organization through the Projects page. When opening a project, you can:

Directly add members to a project, and see a list of members and their roles within a project.
See the billing status, the associated costs and your usage over time for all Nebula resources that you employ in a project.
Monitor user activity within a project through Audit logs.

You can manage team members and invites on the Access manager page. When checking a team member’s details, you can:

Add or remove a user’s access to different projects.
Modify their role in the projects they have access to.

Make sure you understand the scope of each role’s permissions in case you want to change a team member’s role. Remember that organization and project owners cannot be removed from projects unless you change their role first.

Billing and payments

Nebula bills services on an organization level.

Your organization’s billing details, including the payment method is saved during your onboarding. Team members in Owner, Admin, or Finance Manager roles can modify your billing details.

Nebula bills at the end of each month, on a monthly cycle for every organization. If you joined Nebula mid-month, costs are prorated and calculated proportionally from the moment you start using resources.

Billing starts when you create and use Nebula’s compute or storage resources. For storage, this means that Nebula only bills you after you actually start storing objects in the resource you created.

NebCompute prices are calculated based on the type of instance you create and use over time, per hour.
NebStore prices are based the cumulative size of objects stored within your buckets over time, per month, and the data read, write, and delete operations.

The exact price of a server instance depends on the configuration that you choose The Console gives you a detailed summary of the estimated montly costs when you create a resource. This cost is visible before you provision the server.

Costs and usage are grouped on a project level. You can check the billing status and costs and usage over time for all server and storage instances within a project through the Projects page.

Need help?

If you get stuck or run into anything unclear during your onboarding process, we recommend that you check out the Frequently asked questions page.

If you cannot find what you’re looking for, get in touch with our Support team! We are here to help, and welcome any feedback you might have about the onboarding process.