Welcome to nullplatform!
Here you'll find quick information on how to work with and develop on nullplatform.
- These docs assume your cloud account is already managed by nullplatform. If not, reach out to us and we'll get you onboarded.
- Using GitHub? Make sure to install our GitHub integration app.
Getting started
Start by logging in to your organization's portal at: https://<your-org-slug>.app.nullplatform.io
.
Ask a teammate or your manager to invite you. Or check if your organization supports logging in with an identity provider like Google, Okta, or another supported system.
Organizations, Namespaces, Apps, etc.
In nullplatform there is a basic hierarchy that organizes applications and services:
- Organization: this is the main entity in nullplatform, there's one per customer.
- Account: your organization can have many accounts, they can be used to segregate business units or legal entities under a holding company. Every time you log in you're logged into an account, you can switch to another one through the personal menu on the top right.
- Namespace: namespaces are a logical grouping for applications and usually represent teams or areas (eg: checkout, billing). The main view once you log in is the namespace.
- Application: these are logical units that are normally tied to a repository or, in the case of a mono-repo, to a folder inside a repository.
- Scopes: a scope is the definition of runtime environment where your application can be deployed.
Some use cases for scopes are:
- Regions: for example, segregating traffic from US, UK, Japan, and rest of the world.
- Read vs. Write: another typical use is to scale applications under a read/write segregation, which scopes facilitate.
- Production and Testing: to create these environments for team members to self-serve application testing and QA.
How do I start?
A good way of learning nullplatform is to jump into any namespace (you can create a new one with just a few clicks) and create a new application starting from one of the templates.
Nullplatform can run applications in any language given that it can be containerized to run on server instances or supported by serverless runtimes on the cloud.
To run applications in other technologies, you can edit the Dockerfile on the root of the repository and build images for other languages. For serverless applications you can edit the scope settings and change the runtime.
Next steps
This is just a preview of how to get started, please read the following sections of this documentation where we go into more details and be welcome to nullplatform!
Need help?
If you have questions or need assistance with nullplatform, check out our Support page for more information.