Pre-launch — early access is open

Object storage that stays in Slovenia.

SIS3 gives you the S3 API you already use, hosted in Slovenia. EU data residency, Slovenian jurisdiction, and not a single line of code to rewrite.

  • Standard S3 API
  • Data stays in the EU
  • Built in Slovenia
SI

Slovenia

S3

the API you already speak

SIS3

your data, at home

Why SIS3

Storage that respects where your data lives.

The name says it: SI for Slovenia, S3 for the interface every tool already speaks.

Your data stays in Slovenia

Objects live on servers in Slovenia, inside the EU. Slovenian jurisdiction, GDPR by default, and no surprise transfer to another continent.

It is just S3

Buckets, objects, presigned URLs. Point your existing SDK, CLI or backup tool at SIS3 and keep working the way you already do.

Close to your users

Short round trips for teams in Slovenia and the wider region — and support in your own timezone.

Portable by design

An open standard with familiar semantics and 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.

  1. 1

    Join the list

    Send one email and tell us roughly what you would store. We will reply when the beta opens.

  2. 2

    Point your client

    Set the endpoint to SIS3 and keep the tools you already run — AWS CLI, rclone, or your app's SDK.

  3. 3

    Move your data

    Sync buckets with the same commands you use today. Copy in, copy out, no rewrite.

The API

One endpoint. Your existing tooling.

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; the final hostname and credentials arrive with the beta.

point any S3 client at SIS3
# 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-bucket

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.