Security & deployment

Runs in your environment. Reads, never writes.

CloudRuler is self-hosted, uses read-only access to Oracle Cloud and AWS, and keeps a record of every action taken inside it.

Self-hosted in your environment

CloudRuler runs inside your own cloud or data centre. Your inventory, cost, audit and server data does not leave it.

Read-only access to your clouds

AWS: a read-only IAM role provisioned from a CloudFormation template, plus CUR 2.0 and CloudTrail exports to S3. OCI: read-only IAM policies. CloudRuler never changes your cloud.

Credentials in a vault

Cloud credentials are held in a vault, not in configuration files.

SSO and role-based access

Sign in with your identity provider over OIDC. Each role sees only the modules it is allowed to see, and the AI Assistant respects the same roles.

Platform Activity log

Who did what inside CloudRuler itself, recorded and reviewable.

Signed licence per instance

Each deployment runs on its own signed licence.

No SSH to your servers

Server Audit reads from the cloud’s own monitoring agent (OCI Unified Monitoring Agent today). CloudRuler never logs in to your machines.

Deployment

One deployment for all six modules.

One instance covers inventory, FinOps, audit, IAM posture, network and server audit, for every OCI tenancy and AWS account you connect. Every sync and ingest job is visible in Jobs & Schedules, with runs and logs.

  1. Deploy CloudRuler in your environment.
  2. Connect OCI with read-only policies, and AWS with the provided CloudFormation templates.
  3. Sign in with SSO and assign roles.
  4. Classify resources to your landscapes. The modules fill in from there.

Certifications

Need our security documentation for a vendor review? Contact us and we will send it.

Talk to us about deploying CloudRuler.

A 30-minute walkthrough on Oracle Cloud, AWS, or both. Bring your questions about inventory, cost or audit.