InfrayardMake cluster delivery repeatable.
Publish approved templates so teams can request standard configurations without assembling each deployment by hand.
For platform teams running Oracle Kubernetes Engine
Self-service Kubernetes on Oracle Cloud.
Your team stays in control.
Let engineers create and operate OKE clusters through a simple portal. Define approved templates, access and resource limits inside your own OCI tenancy.
A 30-minute product walkthrough, with time for your OCI environment.
- Approved templates
- Cost estimates before deployment
- Runs in your tenancy
See a cluster deployment in action.From template selection and cost preview to a running OKE cluster. Watch the full demo →Music: Dream Culture — Kevin MacLeod · CC BY 4.0. Trimmed, volume adjusted and faded.
Built for Oracle Cloud Infrastructure + OKEOracle Cloud resources are billed directly by Oracle.
A simpler OKE workflow
Spend less time on repeatable infrastructure work.
Give engineers a consistent way to get the clusters they need, with the controls your platform team requires.
Keep access and resources under control.
Define roles and limits. Review protected destroy requests and requests for higher limits in one place.
See estimated costs before deployment.
Make resource choices and estimated spend visible in the same workflow, before and after a cluster is created.
The product in practice
From an approved template to an OKE cluster.
01 / Choose
Start with a template.
Use a configuration approved by your platform team.
02 / Review
Check the request.
Review resources, limits and estimated costs before deployment.
03 / Operate
Manage the lifecycle.
Access clusters, adjust capacity and run supported upgrade and cleanup workflows.
Real screens from the recorded demo. Terraform runs underneath, with logs available to inspect.Explore cluster workflows →
Your environment. Your rules.
Your infrastructure stays under your control.
Infrayard runs in your environment without a Solvia-hosted SaaS control plane. OCI credentials, Terraform state and operational records stay within your managed environment.
Built by Solvia Lab. Infrayard grew out of hands-on work with enterprise cloud infrastructure. Speak directly with the founder about your workflow and deployment requirements.
Use your identity provider.
Connect your organisation’s login system and control access through roles.
Work with your network design.
Use supported existing compartments, VCNs and subnets. Review the requirements before deployment.
Keep operations traceable.
Inspect lifecycle activity, protected requests and execution logs.
Pricing
Start monthly.
Save when you go annual.
Commercial software in your environment.
Choose the commitment that fits your team.
Founding customer offer — 40% off your first year.
For the first five qualifying customers. Programme terms →
Business
For teams standardising OKE delivery and operating their own infrastructure.
€3,000/month
Billed monthly. Cancel at the end of your billing period.
Founding rate for your first 12 months. Renewal uses the standard rate agreed in your order.
- OKE provisioning and lifecycle workflows
- Templates, access controls and resource limits
- Protected requests and activity history
- Cost estimates and execution logs
- Onboarding workshop and email support
Enterprise
For additional rollout, support and procurement requirements.
From€6,500/month
Scope, billing and commitment agreed in your proposal.
- Everything in Business
- Deployment and rollout assistance
- Support arrangements for your organisation
- Delivery and procurement requirements
Support scope and response times are agreed in writing.
Prices in EUR. Oracle Cloud usage is billed separately. Subscription scope →
Need an evaluation first? An optional guided 30-day, non-production evaluation costs €1,500. The fee is credited towards your first production invoice when you convert within 30 days after the evaluation ends.
See evaluation details →A few practical answers
Before we talk.
Technical requirements and operating details are available in the docs.
Explore the documentation →Do engineers need to write Terraform?
Engineers use the portal and approved templates. Platform administrators configure the OCI environment and can inspect the underlying Terraform execution logs.
Explore cluster workflows →What do we need to deploy Infrayard?
A supported Kubernetes environment, OCI credentials and permissions, an identity configuration and the required network connectivity. Your onboarding includes a review of these prerequisites.
View deployment requirements →Can we use our existing network?
Yes. Supported configurations can use existing OCI compartments, VCNs and subnets. Routing, permissions and endpoint connectivity must meet the documented requirements.
Review network configurations →Does Infrayard deploy our applications?
Infrayard focuses on OKE infrastructure and cluster lifecycle workflows. Application deployment and workload operations remain part of your existing delivery process.
See the supported scope →How do we get started?
Request a demo to see the product and discuss your environment. You can then start a monthly production subscription or arrange an optional guided evaluation.
Read subscription and evaluation details →See how Infrayard fits your OKE workflow.
Walk through a real deployment and discuss the templates, access controls and network requirements your team needs.