Common questions, answered clearly.

Devopsify is an infrastructure control plane for bringing multi-cloud, on-prem, and delivery operations into a governed workspace.

Yes. The demo workspace uses mock infrastructure data, so evaluation does not require external cloud credentials or connected accounts.

Public evaluation is limited to protect capacity. Answer the pricing survey to match a plan and request a guided workspace, and the Devopsify team will follow up to confirm scope and terms.

The demo uses mock adapters and demo signals so you can evaluate workflows end to end. Production use connects real environments, and demo estimates should be validated against connected billing sources.

No. AI assistance can investigate context and propose next steps, but authorization remains with server-side controls, policy, scoped capabilities, approval, and audit.

The assistant investigates infrastructure context and proposes a next step within explicit action boundaries. Actions stay scoped to approved capabilities, subject to policy and human review, and are recorded in the audit trail.

Secrets are encrypted (AES-256-GCM), masked, and never logged or sent to model context. Demo evaluation runs without cloud credentials.

Authorization, entitlements, and policy checks run server-side on every operation, scoped to your tenant. Devopsify never trusts a client-supplied organization.

Provider adapters cover AWS, Azure, Google Cloud, and on-prem agent pools, plus Hetzner, DigitalOcean, OVH, and Oracle adapters. Kubernetes and CI/CD signals can also be connected.

On-prem agents run in your environment and report inventory, topology, and signals back to the hosted control plane, giving one governed view across cloud and on-prem.

No. Devopsify is built for multi-cloud and hybrid estates, so workloads can stay where they run while operations, policy, and audit are unified.

Yes. The control plane is hosted by Devopsify and shared across tenants, with each tenant isolated server-side. On-prem agents run inside your environment and report inventory, topology, and signals back to the hosted control plane. A fully self-hosted control plane is not currently offered.

One resource is a managed unit in your inventory, such as a VM or instance, Kubernetes node, database, bucket, load balancer, or serverless function. Cloud, on-prem, and edge resources all count.

Flex is pay-as-you-go at $1.25 per resource per month. Standard is $2,500/mo and includes 3,000 resources. Scale is $3,200/mo and includes 4,500 resources.

Yes, prepaying annually saves 12%. Annual prepay for Standard is $26,400/yr and for Scale is $33,792/yr.

Plans and billing above are illustrative starting points. Committed and tailored agreements are quoted against confirmed scope, and final terms are issued when access is granted.

Plans, policies, approval requirements, scoped capabilities, and audit records are designed to keep operational actions accountable. Every request carries a policy pass, deny, or review signal.

A deployment wave groups related infrastructure changes so teams can review scope, health, and progress together, and coordinate approval and execution.

The audit retains approvals, policy results, execution records, and actor identity so every decision and outcome is traceable.

Runbooks document repeatable response steps while preserving approvals, policy results, execution records, and actor identity for review.

You can create infrastructure plans through OpenTofu, attach approval requirements, and retain the decision trail before apply.

Yes. On-prem agents and repository workflows bring deployments, jobs, and environment signals into the same control plane.

Devopsify surfaces observed drift, utilization, and cost movement beside the resources and decisions that may explain them.

Related resources and service dependencies are traced so reviewers can frame the likely impact of a proposed change before approving it.