Slovenian jurisdiction
Objects stay on servers in Slovenia, inside the EU. Slovenian law and GDPR from day one, with no transfer to another continent.
S3-compatible object storage in Slovenia
Your data, at home in Slovenia.
SIS3 speaks the S3 API your tools already understand, and keeps every object on servers in Slovenia — inside the EU, under Slovenian jurisdiction, with no rewrite required.
Pre-launch. First buckets are being built now — the list gets first invites.
$ aws s3 sync ./backup s3://my-bucket \
--endpoint-url https://s3.sis3.si
upload: ./db.sql -> s3://my-bucket/db.sql
upload: ./assets.tar -> s3://my-bucket/
$ Works with
- AWS CLI
- rclone
- s5cmd
- boto3
- MinIO client
- Your S3 SDK
Why SIS3
Built where your data has to live.
SIS3 is SI plus S3: Slovenia for the location, S3 for the interface. The name is the whole pitch.
The standard S3 API
Buckets, objects, multipart uploads and presigned URLs. Tools and SDKs you already use keep working unchanged.
Close to your users
Short round trips for teams in Slovenia and the wider region, and support in your own timezone.
Portable by design
Open standard, familiar semantics, no proprietary layer. If you ever leave, your data moves with the tools you already have.
How it works
Three steps, none of them a migration project.
-
01
Join the list
Send one email with roughly what you would store. We reply when the beta opens.
-
02
Point your client
Set the endpoint to SIS3 and keep running AWS CLI, rclone, or your app's SDK.
-
03
Move your data
Sync buckets with the same commands you use today. Copy in, copy out, no rewrite.
The endpoint
One URL stands between you and home.
Anything that speaks S3 should work: the AWS CLI, rclone, s5cmd, boto3, the JavaScript and Go SDKs, and the backup tool you forgot you had configured.
The endpoint shown is illustrative; credentials and the final hostname arrive with the beta.
# set it once, use every tool
export AWS_ENDPOINT_URL=https://s3.sis3.si
# then your usual commands
aws s3 ls
aws s3 sync ./backup s3://my-bucketEarly access
Get in before the first bucket.
We are building SIS3 right now. Tell us what you would store and roughly how much, and we will write back when the beta opens.
Email hello@sis3.siNo form, no tracking — the button opens your mail client.
FAQ
Questions, answered plainly.
When can I use it?
We started building in late 2026. Early access rolls out as capacity comes online; the list gets first invitations before anything is public.
Is it really S3-compatible?
The standard S3 API — buckets, objects, multipart uploads and presigned URLs. Clients that speak S3 should work unchanged. Any gaps will be documented before launch.
Where exactly is my data?
On servers in Slovenia, within the EU. We will name the facility and publish our data processing terms before the beta opens.
What will it cost?
Pricing is not settled yet. Early access users will help shape it, and there will be a free tier for testing.
How do I move data in and out?
With the tools you already use: AWS CLI, rclone, s5cmd, or an S3 SDK. Copy in, copy out, with no proprietary export step.
Who is behind SIS3?
A small independent team in Slovenia, building the service we wanted to use ourselves.