Volume based
You pay for the data you store and the traffic you use. We do not ask for an upfront commitment on capacity you will not need.
Service · Storage
S3 storage and backup
Move your images, media and files without loading your server; manage, retain and restore your backups. S3 API compatible object storage, CDN delivery and an encrypted backup schedule arrive as one setup.
- S3 API
- compatible
- AES-256
- encrypted at rest
- Daily
- backup schedule
- TR / EU
- data location
Scope
What the service covers
Storage, delivery and backup are part of the same setup. You do not have to buy three things and wire them together.
-
S3 API compatibility
Your existing SDKs and tools keep working: AWS SDK, MinIO client, rclone, s3fs and any S3-aware plugin. Usually the only things that change are the endpoint and the access key.
-
One-off migration
Files from your current system are copied and verified with checksums before the switch. The old copy stays in place until the new layout is validated, so downtime stays near zero.
-
CDN delivery
Images, video and static files are served from the node closest to the visitor. International traffic gets the same load speed as local traffic.
-
Versioned object retention
The previous version of a deleted or overwritten file is kept for the retention window and can be recalled. A wrong command becomes a reversible event.
-
Backup schedule
Daily, hourly or on demand — including a manual snapshot before a release. The frequency is chosen against the data-loss window you are willing to accept.
-
AES-256 encrypted storage
Backups are encrypted at rest with AES-256 and transferred over TLS. Key management can be separated on request.
-
Monthly restore test
Every month an automated restore runs in an isolated environment, integrity is verified and the result is reported. We do not count an untested backup as a backup.
-
Key and permission management
Each application and team gets its own access key, with permissions defined per folder and per operation. Key revocation and rotation are part of the setup.
-
Choice of data location
You decide whether the data sits in Türkiye or in the European Union. The decision is made alongside your KVKK and GDPR obligations and written into the contract.
-
Monitoring and alerting
Capacity, error rate, latency and failed backup jobs are monitored. If a backup did not run, an email alert goes out without waiting for the monthly report.
-
Reporting panel
How much each bucket holds, when each backup ran, what the restore test returned — all on one screen, with a monthly summary.
2 minutes · 4 questions
Is your data genuinely backed up?
Four questions about how your backups run. If everything is already handled, we will tell you that too.
Before / after
How server load changes
When media leaves the application server, storage location is not the only thing that changes. Disk, CPU, bandwidth and backup size all ease at once.
Disk usage
Before
As user uploads grow, the server disk fills up unpredictably. Expanding capacity usually happens at midnight, under pressure.
After
Files grow inside the object store while the application server disk stays at the size of the application itself. Capacity planning stops being a maintenance task.
CPU and memory
Before
Image resizing, thumbnail generation and static file serving share the same cores as your application processes. At peak hours the request queue grows.
After
File serving leaves the server entirely; CPU and memory work on application logic only. The same hardware handles noticeably more concurrent requests.
Bandwidth
Before
Images and video consume most of the outbound traffic. Your own API responses queue up behind that traffic.
After
Media is delivered from CDN nodes and never touches the server link. All remaining bandwidth belongs to application traffic.
Backup size
Before
Because the backup also covers the media folder, it keeps growing. Backup windows stretch, restores run for hours and retention cost inflates.
After
The backup covers only the application and the database. A smaller backup can be taken more often and restored far faster when something goes wrong.
Outage and recovery
Before
When the server goes down, the application and the media become unreachable at the same time. Recovery waits for terabytes of files to be copied back.
After
Even if the server is rebuilt from scratch, the media stays where it is. Recovery is just bringing the application back up, so availability goes up.
In one sentence: the same hardware serves more users, a smaller backup can be taken more often, and recovery time drops when something breaks.
Process
Five steps to go live
Each step has a defined output. You never have to ask where the project stands.
- 01
Inventory and measurement
How many GB per folder, how often each file type is read, how much egress per month — the current state is measured, not estimated.
- 02
Storage provisioning and keys
Bucket layout, folder scheme, access keys and permission policies are set up. Data location — Türkiye or EU — is chosen at this step.
- 03
Migration
Existing files are moved with verification, and the application switches to the S3 endpoint and CDN addresses. The old copy stays until validation is complete.
- 04
Backup schedule and encryption
Frequency, retention period and versioning rules are defined; backups are encrypted with AES-256 and transferred over TLS.
- 05
Monitoring and monthly restore test
Capacity, error and latency alerts go live. Every month a restore test runs in an isolated environment and the result is reported.
Pricing policy
Volume based · one-page quote
Migration is one-off
Moving from your current system appears as its own line in the quote. It is not folded into the monthly fee and it does not resurface later.
Annual agreement, one-page quote
Storage, traffic, backup schedule, monitoring and the monthly restore test are in the same quote. The service runs on a 12-month agreement: unit pricing does not change during the year, and at the end of it scope and price are reviewed together before renewal. We do not send follow-up surprise invoices.
FAQ
Frequently asked
Do I have to change my existing code?
The storage is S3 API compatible, so the AWS SDK, MinIO client, rclone, s3fs and S3-aware plugins keep working as they are. Normally the only changes are the endpoint, the access key and the place where file URLs are generated. Code changes stay minimal.
Do you handle moving my existing files?
Yes. The migration is planned as a one-off item: files are copied, verified with checksums, and then the application is switched to the new addresses. The old copy is left in place until the new layout is validated.
Can a file deleted by mistake be recovered?
With versioning enabled, yes. The previous version of a deleted or overwritten object is kept for the retention window and can be recalled. How long versions are held is decided together, based on the project.
How often are backups taken?
The default schedule is daily. Hourly schedules can be set up if needed, or a snapshot can be taken on demand before a release. Frequency is chosen against the data-loss window you are willing to accept.
How do I know the backups actually restore?
Every month an automated restore test runs in an isolated environment; the result and the integrity check are reported to you. We do not count an untested backup as a backup.
Where is my data held?
You choose between a Türkiye and a European Union location. The decision is made alongside your KVKK and GDPR obligations and it is written into the contract.
How do you limit who can reach which file?
Each application and team gets its own access key, with permissions defined per folder and per operation. Files that should not be public are served through time-limited signed links, and key revocation and rotation are part of the setup.
Project inquiry
Tell us about your project
Fill in the form and we will get back to you within 1 business day on the channel you choose. Your details are used only for this conversation.