Projects are the smallest useful unit of access in BlockNode. They keep a workload's region, plan, connection URLs, and API keys together.
Use one project per workload
Create separate projects when you want independent limits or billing. Common examples include:
- A production application
- A staging environment
- An indexing pipeline
- A customer-specific integration
This keeps changes easy to reason about and makes it simple to rotate one access key without affecting the rest of the workspace.
Create multiple API keys
Name keys after the application or environment that uses them. A project can have multiple keys, so your team can separate production, staging, local development, and automation.
When a key should no longer be used, revoke it from the project. Keys are shown with their status and creation details so the team can keep access tidy.
Share access safely
Workspace owners and admins can invite members and configure permissions. Project access can be read-only or writable, and billing settings can be limited to the people responsible for them.
Use the smallest project and permission scope that fits the job. It keeps ownership clear as the workspace grows.
Connection URLs
The project overview lists one HTTP URL and one WebSocket URL for each enabled chain. The URLs are region-aware and ready to copy into your application configuration.