Skip to content
Cloud

Cloud services built for people and agents

Build artifacts, store images, and connect services through one Cloud Project. Use the Cloud Console or work directly through the API and CLI.

my-app
Illustrative Project
Build

Source becomes an OCI artifact that can be stored and used by downstream tools.

Learn more
Project boundaryAccess · Resources · Usage
An illustrative resource model, not a live deployment.

One Project

A clear home for resources and service usage.

Explicit access

Permissions for the people and software that need them.

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

Build and run

Turn source code into an immutable OCI artifact.

Run

Build and run

Deploy workloads and manage their revisions.

Sandbox

Build and run

Run commands in durable cloud environments.

Container Registry

Store and connect

Store and distribute Project-owned OCI images.

Databases

Store and connect

Provision isolated, managed PostgreSQL databases.

Domains

Store and connect

Verify domain ownership and claim hostnames.

Pub/Sub

Store and connect

Publish messages and consume them through subscriptions.

Secrets

Secure and manage

Manage write-only runtime secrets and their versions.

IAM

Secure and manage

Control access to Project resources with policies.

OAuth

Secure and manage

Register clients and authorize application access.

Service Usage

Secure and manage

Enable services and inspect usage for a Project.

Analytics

Secure and manage

Collect events and query reports in datasets.

This 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.

Enable what you need

Choose from the services available to your Account. A Project records which capabilities your application can use.

Keep access intentional

Use IAM policies and Project-owned OAuth clients to control who can act and what an application can access.

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.

CLI · project
socra project create my-app

Create a Project in your current Account. Use the Project ID returned by the command in the next steps.

Good to know

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.

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