Douklar 4.0.0, 23 October 2026.A new CLI, douklar, and retry of unfinished objects from a finished S3 Batch job.Read the release notes

Douklar
Get started

Move your data between accounts, and keep the record.

Douklar starts with AWS. It maps ECR images, S3 objects, CodeCommit repositories and DynamoDB items to where they go, shows the plan before anything runs, and keeps every run in Activity, failed ones too.

Read the docsDoes it fit your move?

Other cloud platforms are next. Request yours

Click anywhere here and a little D jumps into the bucket.

Step 1 of 5

One profile per account

Add each AWS account as a profile, with keys or an SSO session. Douklar holds one profile per account, so a move works when the accounts share no Organization or owner.

Accounts and credentials
Douklar console Accounts page: two sample accounts, production and dr, each waiting for keys or an SSO session before it can be used.Douklar console Accounts page: two sample accounts, production and dr, each waiting for keys or an SSO session before it can be used.

Accounts

Captured from the console with sample data.

Step 2 of 5

Map what goes where

Pick what moves and where it lands. Destinations are suggested from your cross-account defaults; edit a whole table as YAML or add mappings one by one.

What moves
Missing or changed objects
Your choices
Worker relay, server-side copy, S3 Batch Operations or a local-file upload; keep object tags if you want them
Amazon S3 in detail
Douklar console Mappings page: tabs per service and a table of ECR mappings.Douklar console Mappings page: tabs per service and a table of ECR mappings.

Mappings

  • Destinations are suggested from your cross-account defaults.

  • ECR, S3, CodeCommit and DynamoDB each have a table, with a count on the tab.

  • Edit a whole table as YAML, or add mappings one by one.

Captured from the console with sample data.

Step 3 of 5

See the plan before it runs

Every run goes through three steps: choose the scope, review the plan, then run it. Preflight reads without writing, and the review lists every write.

Preflight and review
Douklar console Sync page: a Scope, Review, Run stepper with a cross-account source account and one selected target account.Douklar console Sync page: a Scope, Review, Run stepper with a cross-account source account and one selected target account.

Sync

  • Every run goes through three steps: choose the scope, review the plan, then run it.

  • Pick the mode. Regions for ECR, CodeCommit and DynamoDB are set here; S3 bucket Regions are found for you.

  • One run can copy to more than one target account.

Captured from the console with sample data.

Step 4 of 5

Run it, and see it arrive

A reviewed run is queued and run, then each service checks its own result.

Amazon S3
Missing or changed objects, by relay, server-side copy, S3 Batch or upload
Amazon DynamoDB
Only missing items are written, then read back one by one
Amazon ECR
Tags with their referrer graph, checked after every tag
AWS CodeCommit
Branches and tags, mirror or incremental; refs compared at the end
Running a sync
Douklar console S3 Batch page: jobs that are running, failed, complete, and one ready to start with a Start job button.Douklar console S3 Batch page: jobs that are running, failed, complete, and one ready to start with a Start job button.

S3 Batch

  • A job that is ready waits for you: it runs when you press Start job.

  • Each job shows whether AWS generated its manifest or it came from a CSV.

  • The list holds the jobs this console created; jobs made elsewhere in AWS are not listed.

Captured from the console with sample data.

Step 5 of 5

Keep the record

Every run stays in Activity with its route, state and duration, newest first. A failed run keeps its place beside the completed ones.

Activity and evidence
Douklar console Activity page: completed and failed runs with start time, route and duration.Douklar console Activity page: completed and failed runs with start time, route and duration.

Activity

  • Running, completed, warning, failed or cancelled.

  • A failed run keeps its place beside the completed ones, newest first.

  • Source to destination; "+1" marks a run that went to one more target.

Captured from the console with sample data.

Does it fit your move?

Pick what moves, how often and between which accounts. When an AWS service does the job better, the answer names it.

What moves?
How often?
Between which accounts?
Douklar fits this move.
  • ECR imagesDouklarCopies the tags you pick, with their referrers, into an existing repository.
  • S3 objectsDouklarCopies missing or changed objects; objects only in the destination stay.

Carve-out or merger: what usually moves

Who makes Douklar

Douklar is created and maintained by Nijat Hummatović (Hummatovic), a cloud and DevOps engineer working with AWS, Terraform and Kubernetes.

Douklar is AGPL-3.0-or-later for now; the licence can change before the public release. A commercial licence covers rebranding, white-labelling, resale or hosting. For a licence, a pilot on a real move, or working together, write to douklar@hummatovic.com.

Run it on your machine

One script starts the console, its worker and a database on a Linux host with Docker. The source repository is not public yet; the install guide is written for people who have access.

Read the install guide

./install.sh local
Host
Linux x86_64 with Docker
Database
PostgreSQL: local Docker, external, Amazon RDS or Supabase
Sign-in
Bundled or external ZITADEL, or Amazon Cognito
Roles
Admin, operator and viewer, mapped from your identity provider

Keyboard shortcuts

g h
Home
g c
The console
g m
Use cases
g d
Docs
g r
Releases
/ or Ctrl K
Search the docs (on docs pages)
t
Switch light and dark
?
Show this list