Obscura Flow
Menu
Contact

Studios

A shared method, not an oral convention.

In a studio, the way to name, file, and archive already exists. It simply lives in two or three people's heads, and is lost with every departure.

Talk to usDocumentation

In short

A studio produces fast and archives late. Obscura Flow makes the filing method explicit: normalized projects, a shared thesaurus, persistent inventory numbers, and sealed archives, so knowledge no longer rests on one person's memory.

  • Shared thesaurus instead of improvised keywords
  • Inventory numbers in PREFIX_YEAR_sequence form
  • Explicit project lifecycle: draft, active, archived
  • Sealed archives and verified off-site copies
  • Metadata in sidecars, readable by other tools

What gets lost without a written method

The cost does not show during production, but when retrieving, re-invoicing, or handing over a file.

Naming convention
It changes with the people, and nobody rewrites history.
Vocabulary
Everyone tags with their own terms, which makes cross-cutting search impossible.
Progress state
Without an explicit lifecycle, nobody knows what is delivered, archived, or pending.
Location
The file exists, but on which drive, in what state, with which approved version?

Making the method executable

A method written in a shared document is followed halfway. A method embedded in the tool applies by default.

Numbering
A persistent identifier assigned on entry, independent of file names and reorganizations.
Controlled vocabulary
Free keywords are promoted into the thesaurus after review, instead of proliferating.
Smart collections
A rule describes what belongs together, rather than a manual selection someone must maintain.
Scheduled audits
Integrity checking no longer depends on someone being available.

Questions

Can it handle large archives?

Yes. SQLite cataloging, virtualized galleries, and parallel processing remain usable on tens of thousands of images.

Are EXIF/IPTC/XMP metadata supported?

Yes. They are read through ImageIO, and ExifTool when available, and underpin cataloging, search, migration, and preservation.

Which backup destinations are supported?

Amazon S3, Backblaze B2, Cloudflare R2, any S3-compatible storage, NAS, and local folders for a 3-2-1 strategy.

How is archive integrity verified?

Each archive includes a SHA-256 manifest and an Ed25519 signature. Scheduled fixity audits and format validation reveal drift or corruption.

How do I get support?

For a studio or institution, we can help with framing, migration, and integration. Use the contact page to describe your context.

How is this different from an enterprise DAM?

An enterprise DAM is usually an online service centered on distribution and rights, billed per seat. Obscura Flow is a local application centered on documenting and preserving a photographic body of work, usable offline.

Continue

Photo DAM

What separates this approach from an enterprise DAM.

Full workflow

The eight steps, from import to restore.

Photo archive

Sealing and verifying delivered work.

Decision

Build an archive that stays understandable.

Tell us about your context before the public opening of downloads and commercial offers.

Book a meetingRead the documentation