Run your storage alongside your app on Google Cloud.Run your storage alongside your app on Google Cloud.
Run Keldra on your own Google Cloud Compute Engine instances with persistent disks. Keep object storage close to your applications, use familiar S3-compatible tools and keep control of your service.
Same product. Your environment. Your data.
Store. Find. Control.
Object storage for real work.
Google Cloud
Your application
Connect over your chosen network
Compute Engine
Your Keldra instances
Persistent Disk
Your provisioned storage
Built for real-world use on Google Cloud
Choose where your object storage runs without making a different storage product part of each environment.
Deploy the same product across environments
Use the same Keldra release locally, in your data centre and on Google Cloud. Test the instance and disk configuration your workload needs.
Integrate with your existing tools
Connect applications through Keldra’s supported S3 operations and AWS Signature Version 4 authentication. Check the compatibility list before moving a workflow.
Control your data placement
Choose your instances, region and network to fit application latency and data residency requirements. Your deployment choices still determine the result.
Know the operator responsibility
Your team owns the Keldra deployment, configuration, access controls, updates and recovery procedures.
Compute Engine and Persistent Disk
Google Cloud
Your application
Connect over your chosen network
↓
Keldra
Running on Compute Engine
↕
Persistent Disk
Your provisioned storage
Your application
Connect over your chosen network
→
Keldra
Running on Compute Engine
↔
Persistent Disk
Your provisioned storage
Inside your Google Cloud project
Migrate your data with familiar operations
Use an object migration tool with the correct source and destination credentials. Test object names, metadata, versions, multipart uploads and permissions before moving a production workload. Keep the source until your checks and recovery plan are complete.
Cloud Storage’s XML API works with some S3 tools using HMAC credentials. The services are not interchangeable: check the operations your tool uses against both endpoints, rather than assuming every S3 feature will transfer.
Understand what you operate
Keldra is self-hosted software, not a Google-managed service. Budget for compute, disks, network traffic, backups and your team’s time; self-hosting is not automatically cheaper.
You operate
Deployment and configuration
Authentication and access controls
Monitoring, updates and capacity
Backups and tested recovery
Google Cloud provides
The infrastructure you purchase: Compute Engine, disks and networking. Those services do not operate or back up your Keldra application for you.
Review provider charges and API differences alongside Keldra’s supported-operation list.
Get started on Google Cloud.
Download Keldra and deploy it in your own environment.