What is a Cloud Project?
A Project groups an application’s resources, enabled services, and usage within your Account. Create separate Projects when you need separate resource and access boundaries.
Cloud infrastructure for the agentic era
Build artifacts, store images, and connect services through one Cloud Project. Use the console or work directly through the API and CLI.
my-app
Illustrative projectBuild
Source becomes an OCI artifact that can be stored and used by downstream tools.
Read the referenceProject boundaryAccess · Resources · Usage
01
One Project
A clear home for resources and service usage.
02
Explicit access
Permissions for the people and software that need them.
03
Direct interfaces
The same service contracts behind your tools.
Choose what your system needs.
Independent capabilities, organized around your Project. Explore the services and go straight to their documentation.
Build
Turn source code into an immutable OCI artifact.
Build and runRun
Deploy workloads and manage their revisions.
Build and runSandbox
Run commands in durable cloud environments.
Build and runContainer Registry
Store and distribute Project-owned OCI images.
Store and connectDatabases
Provision isolated, managed PostgreSQL databases.
Store and connectDomains
Verify domain ownership and claim hostnames.
Store and connectPub/Sub
Publish messages and consume them through subscriptions.
Store and connectSecrets
Manage write-only runtime secrets and their versions.
Secure and manageIAM
Control access to Project resources with policies.
Secure and manageOAuth
Register clients and authorize application access.
Secure and manageService Usage
Enable services and inspect usage for a Project.
Secure and manageAnalytics
Collect events and query reports in datasets.
Secure and manageThis catalog describes Cloud capabilities. Service access depends on your Account and Project. Check the Cloud Console for the services available to you.
Your system starts with a Project.
Give each application a home. Enable its services, define access, and keep its resources and usage together.
Understand Projects01
Enable what you need
Choose from the services available to your Account. A Project records which capabilities your application can use.
02
Keep access intentional
Use IAM policies and Project-owned OAuth clients to control who can act and what an application can access.
03
See where usage belongs
Inspect service usage by Project. Your Account remains the place for billing and payment administration.
Go from an idea to a command.
Work from your terminal or let a coding agent use the same CLI. Every service has a focused reference for its resources and operations.
socra project create my-appCreate a Project in your current Account. Use the Project ID returned by the command in the next steps.
Open documentationGood to know.
Can a coding agent use Cloud?
A coding agent with terminal access can use the Socra CLI. Applications can integrate with service APIs directly. Access is still controlled by the credentials and permissions you grant.
Are all of these services available to my Account?
Not necessarily. Some services are restricted to particular Accounts or Projects. The Cloud Console shows your available services; the documentation explains their interfaces.
Where do I manage billing?
Your Account owns billing. Use Admin to manage payments and inspect costs, while Projects identify which application consumed a service.
Cloud infrastructure for the agentic era
Cloud services built for people and agents
Open Cloud Console