BYOS research

Modified: February 14, 2026 7:58 PM Created: September 17, 2025 3:27 PM Master Type: Notes Hide: No Starred: No Status: Unassigned

Here are several Digital Asset Management Systems (DAMS) that let you bring your own storage (BYOS), so you pay for the DAM interface/functionality but keep assets in your existing infrastructure—particularly Google Drive:

1. Pics.io DAM

• Built as an overlay on Google Drive, Pics.io lets you manage assets in Google Drive without migrating them. You retain your storage; Pics.io adds metadata, tagging, search, version control, portals, and richer permissions—all through Drive permissions and API access only (Pics.io).
• It’s explicitly pitched to museums, archives, libraries, and galleries (GLAM) and offers nonprofit pricing and GLAM-focused features like provenance metadata and public sharing portals (Pics.io).
• You pay only for Pics.io licensing; assets stay in Drive and the integration avoids vendor lock-in (Pics.io, Pics.io - DAM insights and news).
• A user on Reddit noted finding Pics.io as “a great DAM… uses Google Drive as a storage database rather than you having to purchase separate storage” (Reddit).

Why it fits your needs

• Works natively with Google Drive as storage
• Designed with GLAM use cases in mind
• BYOS model—pay only for the DAM interface
• No need to migrate assets; Drive remains single source of truth

2. Damvia

• An open-source DAM layer that sits on top of existing cloud storage (including Google Drive, Dropbox, and SharePoint) and does not require asset migration (Reddit, Pics.io, Reddit).
• It’s especially noted for CPG and ecommerce use, but the underlying BYOS model makes it applicable to any use case—including museums/archives.
• Includes basic DAM functions (tagging, product linking, search, customizable asset pages) without needing proprietary storage (Reddit).

3. ResourceSpace (and other open-source DAMs)

• Widely used by libraries, archives, universities. ResourceSpace is free and self‑hosted, meaning you install it on your own servers and connect it to your existing storage infrastructure (local servers or cloud) (Reddit).
• Even though it doesn’t integrate directly with Google Drive, your organization could mount Drive (or sync) on your server and let ResourceSpace catalog it—thus achieving BYOS in practice.
• Other open-source options like Photoprism or bespoke systems may similarly be adapted to use your existing storage (Reddit).

4. Other tools with integrations

• IT automation platforms like Acquia DAM or Sprinklr DAM offer Google Drive integrations, syncing new files from Drive into their DAM backend. However, they also require you to host assets within their ecosystem, meaning you’re not truly just using your Drive for storage—so these are less fitting for a pure BYOS scenario (Acquia, sprinklr.com).

🧪 Quick Comparison

✅ Recommendation Summary

• If you want minimal migration work, native Google Drive support, and nonprofit/GLAM pricing, Pics.io is the most polished and ready-to-use solution.
• If you prefer open-source control, flexibility, and the ability to self‑host, Damvia and ResourceSpace are strong alternatives—though some integration work may be required to connect them to Drive storage.
• Other enterprise DAM platforms integrate with Drive but typically require syncing into proprietary storage, which contradicts BYOS.

🔍 Want to go deeper?

• I can help guide you through Pics.io pricing tiers, its metadata model for museum catalogs, or how to test it with a free trial.
• If you’re up for DIY, I can also walk you through installing ResourceSpace or Damvia and connecting them to Google Drive or existing archival storage.
• Let me know if you’d also like recommendations for DAMs that support other storage types like Amazon S3 or local servers!

Absolutely! Let’s dive into your three requests one by one:

1. Pics.io Pricing, Metadata Model, and Free Trial

Pricing Tiers (as of July 2025):

Pics.io offers four transparent plans (G2):

• Solo – $100/month: 1 user (extras $25/user), core DAM features, unlimited BYOS (Google Drive or Amazon S3) or 100 GB Pics.io storage.
• Micro – $225/month: Up to 10 users ($20/user), 1 TB BYOS or Pics.io storage; adds portals, version control, custom fields, commenting, roles/permissions, inbox uploads, optional AI toolkit, and 24/7 support.
• Small – $680/month: Up to 50 users ($15/user), 3 TB storage; adds branding, watermarks, API access.
• Enterprise – Custom pricing: Over 100 users, Okta SSO, metadata recovery, advanced analytics, training, etc.

They include a 7-day free trial on the Solo plan when you sign up—no credit card required (crozdesk.com, G2, crozdesk.com, Pics.io - DAM insights and news).

Metadata Model for Museum/Archive Use:

• Supports standard metadata schemas like EXIF/XMP embedded in files.
• You can add custom metadata fields (e.g. accession number, provenance, conservation status, creator, date, rights).
• Rich search/filtering based on keywords, custom fields, and file attributes.
• Version control, commenting, and sharing portals allow workflow and public-facing collections (Pics.io).

How to Test It:

1. Sign up on Pics.io to start the Solo plan free trial.
2. Connect your existing Google Drive or Amazon S3 bucket.
3. Crawl/import assets (Drive remains single source of truth).
4. Define metadata fields relevant to museum catalogs.
5. Batch-tag, create collections/portals, invite collaborators.
6. Explore versioning and portal sharing.
7. At trial end, you can stay on Solo or upgrade to Micro/Small for advanced features.

Their support team’s onboarding resources and training sessions (included in Micro+) can help you configure to archival standards.

2. Installing ResourceSpace or Damvia with Google Drive or Local Storage

ResourceSpace

• Open-source, self-hosted DAM widely used by universities, libraries, and archives (Pics.io - DAM insights and news, Reddit, Reddit, Pics.io).
• To integrate with Google Drive, one typical approach is:
  • Mount Drive via tools like rclone or Google Drive File Stream on your server.
  • Configure ResourceSpace to index and catalog the mounted folder (set the filestore path to that mount).
• Alternatively, assets can reside on local servers or S3 connected directly.
• Installation steps:
  1. Set up server (Ubuntu, LAMP/LEMP stack).
  2. Install ResourceSpace (from source or Docker).
  3. Configure MySQL/MariaDB and point the filestore to your mounted storage.
  4. Customize metadata fields (there’s robust support for Dublin Core, IPTC, type-specific schemas).
  5. Assign user roles/permissions, import assets, test search and sharing workflows.
• Some users reported Docker installs on NAS devices encountering UI issues or duplicate file paths; careful path configuration is key (Reddit, Reddit).

Damvia

• Open-source DAM that acts as a lightweight layer over existing cloud storage like Google Drive, Dropbox, SharePoint.
• Less documentation, but design is simple:
  1. Install Damvia on a web server.
  2. Connect it via API credentials to your Google Drive root or folder.
  3. Damvia exposes a web UI for metadata tagging, search, and asset browsing without syncing/moving files.
• Ideal if you want minimal infrastructure and directly operate on Drive files.

3. Additional Museum/Archive DAMs Supporting S3 or Local Servers

If you’re open to connecting storage beyond Google Drive, here are strong DAMs for museums and archives:

• ResourceSpace – supports local file servers and Amazon S3. Fully metadata‑driven, customizable, open-source, and GLAM-friendly.
• Pics.io – as noted above, seamlessly supports both Google Drive and Amazon S3 as BYOS options (Reddit, Pics.io, Reddit, Pics.io - DAM insights and news).
• Samvera Hyku (based on Fedora/Valkyrie) – open‑source repository/DAM used by libraries and archives. Connects to local/NAS storage or cloud buckets and supports detailed archival metadata ingestion with CSV import @ reddit resource context (Reddit).
• Omeka S – widely used by museums; supports local file storage or external mounts. Focused on exhibitions and collections, with linked open data metadata models.
• Phraseanet – open-source DAM/photobank, often used by cultural institutions; supports self-hosting with filesystem or S3 storage.

✅ Summary Checklist

Would you like step-by-step setup documentation for ResourceSpace or Damvia, sample metadata templates used by archives, or assistance planning a comparison trial (e.g. running Pics.io Micro vs ResourceSpace) on your own infrastructure?

Here’s a deep dive into your requests:

1. Step-by-Step Setup Instructions

📦 ResourceSpace (Self‑hosted on local server or cloud):

1. Prepare your server

   Use Ubuntu LTS (20.04/22.04), with Apache or Nginx, PHP and MySQL/MariaDB. Adjust php.ini to allow large uploads/timeouts (important for high‑resolution archival files) (ResourceSpace).

2. Install ResourceSpace

   • Clone or svn checkout into your web directory.
   • Make filestore/ and include/ writable by the web server.
   • Run browser‑based installer. Provide DB credentials, create admin user, and run the System → Installation Check (ResourceSpace).

3. Connect archive storage

   • Mount Google Drive using rclone mount (or google‑drive‑ocamlfuse) to a directory, e.g. /mnt/gdrive (Damvia, Reddit).
   • Rename or symlink ResourceSpace’s filestore to that mount (or configure $storagedir and $storageurl in config.php) (Google Groups).

4. Metadata & workflow setup

   • Access Admin → Setup → Metadata Fields to define fields like accession number, creator, rights, provenance, conservation status, etc.
   • Import assets, assign resource types, user groups, and define access roles.

5. Best practices

   • Configure cron jobs (e.g. nightly cron_copy_hitcount.php) for relevance-based search ranking (ResourceSpace).
   • Use ImageMagick/FFmpeg for rich previews and thumbnails.

🧩 Damvia (Lightweight overlay on existing cloud storage):

1. Install environment

   Deploy on PHP-capable web server. Use either self-hosted or managed version from Damvia’s site (ResourceSpace, Damvia).

2. Connect to Google Drive

   Provide Google API credentials, point Damvia to root or selected Drive folder—dynamic: no asset migration.

3. Configure fields

   Customize metadata pages, tagging, and regex-based product-data linking. Works well for tagging, search, minimal setup.

4. Use cases

   Best for minimal footprint, quick deployments, and avoiding asset migration.

2. Sample Metadata Templates for Archives / Museums

Here’s a starter schema frequently used by GLAM institutions:

You can export this as CSV for batch metadata import. In ResourceSpace, you’d define each field in Admin → Metadata fields. In Pics.io or Damvia, you can define custom fields and import via CSV or UI.

3. Planning a Comparison Trial

Objective

Compare Pics.io Micro plan vs ResourceSpace on metadata flexibility, ease of setup, search/browsing, GLAM features, and integration with your storage.

Trial Design

Extras

• Consider extending Pics.io trial through support for more time if needed (The Digital Project Manager).
• ResourceSpace has Bitnami images or cloud marketplace VMs to get started quickly with minimal conflicts (ResourceSpace).

✅ Summary

• ResourceSpace: powerful, open-source, customizable, works with Google Drive (via mount), S3 or local servers; ideal for metadata-rich archival use.
• Damvia: lightweight overlay on Google Drive—very minimal install, runs on existing cloud storage, but less feature depth.
• Pics.io Micro: ready-to-go hosted DAM integrated with Drive or S3, fast setup, built-in metadata, portals, and GLAM-friendly; worth trialing given nonprofit discounts.

Would you like step-by-step shell command examples for rclone mounting, configurations for metadata fields in ResourceSpace, or template CSV ready for import? I’m happy to help further.

Absolutely! Here’s a focused guide to help with your three key needs:

1. 🖥️ Step‑by‑Step Shell Commands for Rclone Mount → ResourceSpace Storage

Install & configure your Google Drive remote:

rclone config
# Choose:
#  n) New remote
#  name> gdrive
#  Storage> drive
#  client_id> [press Enter]
#  client_secret> [Enter]
#  scope> 1   # full access
#  service_account_file> [Enter]
#  Use auto config? y
#  Configure Shared Drive? n
#  y to confirm remote

(help.rapidseedbox.com)

Mount your Drive to a directory and allow resource access:

sudo mkdir -p /mnt/gdrive
sudo chown $(whoami) /mnt/gdrive

rclone mount gdrive:/path/to/collection /mnt/gdrive \
  --allow-other \
  --dir-cache-time 168h \
  --vfs-cache-mode writes \
  --vfs-read-chunk-size 64M \
  --vfs-read-chunk-size-limit 2048M \
  --buffer-size 64M \
  --timeout 1h \
  --poll-interval 1m \
  &

This ensures smooth metadata reads/writes and access across users (dediseedbox.com)

To unmount later:

fusermount -u /mnt/gdrive

(Big Bear Community, old.suchicodes.com)

Once mounted at /mnt/gdrive, you can configure ResourceSpace’s filestore to point there.

2. 🔧 Metadata Field Configuration: ResourceSpace & Pics.io

ResourceSpace (via Admin → Setup → Metadata Fields):

You can assign field groups per resource type, set which are required, searchable, or visible in thumbnails.

Pics.io (via Dashboard → Settings → Custom Fields):

• Create fields with types like text input, dropdown, multi‑tag.
• Can map to embedded metadata (e.g. XMP EXIF).
• Options:
  • “Accession Number” (single-line text)
  • “Provenance”
  • “Creator”
  • “Date Created”
  • “Rights / License” (dropdown list)
  • “Keywords” (tag/multi)
  • “Physical Description,” “Conservation” (long text)

Pics.io allows you to import metadata via CSV mapping to these fields or embed via XMP.

3. 📁 Sample CSV Template for Batch Metadata Import

Use this as a starting CSV for ResourceSpace or Pics.io Metadata Batch Import:

Filename,Accession Number,Title,Creator,Date Created,Provenance,Physical Description,Conservation Status,Rights / License,Description,Subject Keywords
IMG001.jpg,ACC‑0001,"Portrait of Donor","Jane Smith","1902-05-15","Donated by Smith family","Oil on canvas; 45×60 cm","Good","Public Domain","A portrait of donor in formal attire.","portrait;donor;smith family"
IMG002.jpg,ACC‑0002,"Ancient Vase","Unknown","-300 to -200 BCE","Excavated at site X","Terracotta; 30 cm high","Fair","Restricted","A Greek vase reconstructed from shards.","ceramics;greek;vase"

• Filename must match exact file name in the mounted folder.
• Map other columns to the custom fields you created.
• Import via ResourceSpace CSV batch upload or via Pics.io’s CSV import tool.

✅ Summary

• Rclone mount commands above let you map Google Drive into a server and serve it as ResourceSpace’s filestore.
• Metadata setup tables show how to configure both ResourceSpace and Pics.io with archive-standard fields.
• The CSV template helps you import consistent structured metadata across platforms.

Let me know if you’d like:

• A full config.php example for ResourceSpace to point to /mnt/gdrive
• A Pics.io field‑mapping walkthrough with screenshots
• A shell script to automate mounting on startup or a systemd unit file example

Here’s what you asked for—organized into three parts:

1. 🛠️ systemd Service File to Auto‑Mount Google Drive with rclone

Create a service file at /etc/systemd/system/rclone-gdrive.service:

[Unit]
Description=Mount Google Drive via rclone
Wants=network-online.target
After=network-online.target

[Service]
Type=simple
User=your_username
ExecStart=/usr/bin/rclone mount gdrive: /mnt/gdrive \
  --config=/home/your_username/.config/rclone/rclone.conf \
  --allow-other \
  --vfs-cache-mode writes \
  --vfs-cache-max-size 10G \
  --vfs-cache-max-age 100h \
  --buffer-size 32M \
  --dir-cache-time 72h \
  --timeout 1h
ExecStop=/bin/fusermount -uz /mnt/gdrive
Restart=on-failure
RestartSec=10

[Install]
WantedBy=multi-user.target

Then enable and start it:

sudo systemctl daemon-reload
sudo systemctl enable --now rclone-gdrive.service
sudo systemctl status rclone-gdrive.service

This will mount your drive at /mnt/gdrive automatically on boot (help.systeme.io, hamradio.my).

2. ResourceSpace config.php to Point Filestore at /mnt/gdrive

Modify your ResourceSpace installation’s include/config.php (copy from config.default.php), adding or editing:

<?php
$mysql_server = 'localhost';
$mysql_username = 'resourcespace_rw';
$mysql_password = 'your_db_password';
$mysql_db       = 'resourcespace';

$storagedir = '/mnt/gdrive/filestore';  // if you want a subfolder
$storageurl = '';    // use if access externally via web server

$filestore_evenspread = true;
$originals_separate_storage = false;
?>

Alternatively, if you prefer not to manipulate filestore spidering logic, you can symlink:

cd /var/www/html/resourcespace
mv filestore filestore.bak
ln -s /mnt/gdrive filestore

Ensure the web server user (e.g. www-data) can read/write to /mnt/gdrive (resourcespace.com).

3. Pics.io Custom Field Mapping Walkthrough

help.pics.io/en/articles…

🚀 Steps to create archive-oriented custom fields in Pics.io:

• In your Pics.io dashboard, go to Settings → Custom Fields.
• Click Add Field, then configure:

• Map each field to embedded XMP tags or assign manually.
• To import metadata via CSV: go to Import → CSV, map each column name to a custom field name.

These components give you:

• ✅ A systemd‑enabled rclone service for automatic Drive mounting
• ✅ A ResourceSpace config to use /mnt/gdrive as the filestore
• ✅ A visual walkthrough for creating archetypal archival metadata fields in Pics.io

Want me to write a full systemd unit file with environment path, or script it for user services? Need sample screenshots for ResourceSpace metadata field setup? Just say the word!

resourcespace.com/knowle…

Here are your detailed resources:

1. Full systemd Unit File (User-specific Service)

Save this as ~/.config/systemd/user/rclone-gdrive.service:

[Unit]
Description=Mount Google Drive via rclone (user service)
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
ExecStart=/usr/bin/rclone mount gdrive: /home/%u/mnt/gdrive \
  --config=/home/%u/.config/rclone/rclone.conf \
  --allow-other \
  --vfs-cache-mode writes \
  --vfs-cache-max-size 10G \
  --vfs-cache-max-age 100h \
  --buffer-size 32M \
  --dir-cache-time 72h \
  --timeout 1h
ExecStop=/usr/bin/fusermount -uz /home/%u/mnt/gdrive
Restart=on-failure
RestartSec=10
Environment=RCLONE_CONFIG=/home/%u/.config/rclone/rclone.conf

[Install]
WantedBy=default.target

Enable and run it using:

systemctl --user daemon-reload
systemctl --user enable rclone-gdrive.service
systemctl --user start rclone-gdrive.service

This mounts Google Drive at /home/your_user/mnt/gdrive on login. Ensure fuse is installed and allow_other is enabled in /etc/fuse.conf.

2. config.php Example for ResourceSpace Filestore

Place in your ResourceSpace include/config.php:

<?php
$mysql_server = 'localhost';
$mysql_username = 'resourcespace_rw';
$mysql_password = 'your_db_password';
$mysql_db       = 'resourcespace';

$storagedir = '/home/your_user/mnt/gdrive/filestore';
$storageurl = '';  // leave empty unless exposing via web

$filestore_evenspread = true;
$originals_separate_storage = false;

// ExifTool integration for metadata
$exiftoolpath = '/usr/bin/exiftool';
?>

Alternatively, you can symlink your existing filestore folder to /home/your_user/mnt/gdrive/filestore to map assets into ResourceSpace.

3. ResourceSpace Metadata Field Setup (Screenshots Provided)

On ResourceSpace Admin → System Setup → Configure Metadata Field:

You’ll see a screen like the top-left image (from turn0image11) where you can add fields such as:

• Accession Number (type: alphanumeric)
• Title (free text)
• Creator / Photographer
• Date Taken (date)
• Location (City, Country) — map IPTC codes like IPTC:City 2#090 (ResourceSpace, ADMIN Magazine, NNC3, Reddit)
• Rights (dropdown controlled)
• Description / Caption
• Subject / Keywords (controlled vocabulary)
• Conservation Notes (long text)

Set each field’s indexing/search/required/display options per best practices (ResourceSpace).

4. Pics.io Screenshots — Backend & Portals

Images (turn0image5 and turn0image6) illustrate the UI of a Pics.io photography archive:

• Asset listing panel with thumbnail previews, metadata quick filters, tag cloud, and folder navigation.
• A sample portal view with filters, collections, and user-friendly layout.

These are representative of a DAM suited for large photography archives (Pics.io).

5. Pics.io Custom Field Mapping for a Historical Photography Archive

Consider these field definitions in Pics.io Settings → Custom Fields:

You can map these to embedded EXIF/XMP when available, and enforce controlled vocabulary and required status for archival consistency.

✅ What You Have:

• A systemd service ready to auto-mount Drive on login/system start
• A ResourceSpace configuration pointing to that Drive-based filestore
• Clear, visual screenshots and guidance to configure metadata fields in ResourceSpace
• Reference Pics.io interface views and a field schema tailored for historical photography archives

Would you like me to generate a ready-to-import CSV template matching the Pics.io fields? Or provide synthetic screenshots/mockups showing portal viewer views with archival metadata filled in?

blog.pics.io/the-most-co…

Here’s everything you requested:

1. 📄 Ready-to-Import CSV Template (Matching Pics.io Field Schema)

Use this CSV to batch-import historical photography archive metadata into Pics.io:

Filename,Accession Number,Photographer,Date Taken,Location (City),Country,Subject Keywords,Description / Caption,Rights / Usage,Conservation Status,Format / Medium,Archive Collection,Negative Number
IMG_A001.jpg,ACC‑1901‑A001,John Doe,1935-07-12,Paris,France,"street;portrait;1930s","Street portrait of a Parisian vendor.","Public Domain","Good","Silver Gelatin Print","Paris Archive","NEG-A001"
IMG_A001_neg.tif,ACC‑1901‑A001‑NEG,John Doe,1935-07-12,Paris,France,"negative;glass plate;John Doe","Original glass plate negative of A001.","Public Domain","Fair","Glass Plate","Paris Archive","NEG-A001"
IMG_B023.jpg,ACC‑1910‑B023,Jane Smith,1910-05-08,New York,USA,"architecture;skyline;1900s","Photograph of Manhattan skyline.","Restricted","Excellent","Albumen Print","NY Archive","NEG-B023"

• Filename must exactly match your Drive file names.
• Column headers correspond to custom field labels defined in Pics.io.
• Includes both photograph and negative assets, sharing accession number and differentiating via file names and negative fields.

2. Synthetic Screenshots / Mockups of Pics.io Portal Viewer

The first image (top-left) simulates the backend asset grid view, displaying thumbnails with metadata sidebars and filters—a typical interface for browsing large archives.

The second (top-right) shows a portal (public web collection) layout: mosaicked thumbnails, filters by keywords or date, and user-friendly access to view/download.

The third (bottom-left) illustrates asset detail popup, metadata field display and image preview consistent with archival descriptions.

The fourth (bottom-right) captures a search results view with tags, filters, and search bar, suitable for exploring a historical photography collection.

These mockups align with Pics.io’s archival UI capabilities (Pics.io - DAM insights and news, Pics.io - DAM insights and news, pics.io).

3. Linking Related Assets in Pics.io (e.g. Photograph and Negative)

Pics.io’s Linked Assets feature lets you connect related files without altering folder structure or metadata taxonomy (medium.com). Here’s how you’d establish relationships for photograph and negative:

1. Upload both assets (IMG_A001.jpg and IMG_A001_neg.tif) via Drive across your Pics.io library.
2. In the asset grid, select both items, then click “Link assets”.
3. The photograph (asset 1a) and negative (asset 1b) will now reference each other.
4. When viewing either asset in detail view, you’ll see a “Linked Assets” panel listing the counterpart—allowing quick navigation between them.
5. If needed, you can remove the link via the “unlink” (X) button.

This method keeps both assets logically connected (e.g. photo plus original negative) and visible during review, cataloging, or sharing workflows.

✅ Summary

• A clean CSV import template mapping to Pics.io custom fields.
• Interface mockups showing backend dashboards and portal interfaces stylized for archival photography collections.
• A clear workflow for linking related assets—perfect for associating photos with their negatives.

If you’d like real PNGs or editable mockups, or want to expand these templates to include multiple negative variants or geospatial metadata mapping, just say the word!

For a large museum archive (30–40 TB), you need a BYOS (Bring Your Own Storage) DAMS that is scalable, metadata-rich, and supports external or local storage like NAS, Amazon S3, or mounted drives (via rclone or NFS). Based on these needs, here are the top 4 recommendations, tailored for large archival use:

✅ 1. ResourceSpace

• Storage Options: Any mounted local storage (e.g. NFS, rclonemounted Google Drive, RAID, NAS)
• BYOS? ✅ Yes (100%)
• Why it’s good:
  • Built specifically for cultural heritage and museum archives
  • Rich custom metadata field support
  • Excellent batch metadata import/export
  • No vendor lock-in; fully open source
• Scale: Proven to support 40+ TB in production with good file architecture
• Cost: Free (self-hosted), or paid cloud plans

🔧 Best for: Museums with IT staff or partners who can host the DAM and maintain local storage.

✅ 2. Phraseanet

• Storage Options: Filesystem, NFS, S3 via plugins
• BYOS? ✅ Yes (filesystem and external storage supported)
• Why it’s good:
  • Open-source, enterprise-grade DAM
  • Excellent for high-volume photography, scanned documents, or video
  • French-language museum and archive institutions use it heavily
• Scale: Supports tens of TBs, multiple storage backends
• Cost: Free (self-hosted), support available via partner companies

🔧 Best for: Archives needing a flexible, browser-based UI with built-in search and processing tools.

✅ 3. EnterMedia (now Razuna)

• Storage Options: Amazon S3, Wasabi, Google Drive (via external mounts), local
• BYOS? ✅ Yes
• Why it’s good:
  • Well-suited for media-heavy archives (audio, video, photos)
  • Modular metadata system
  • Built-in preview generators, custom workflows
• Scale: Deployed for archives >50 TB
• Cost: Open-source self-hosted version, cloud hosted version available

🔧 Best for: Museums with large audiovisual collections or needing asset relationships and custom workflows.

✅ 4. Razuna (Java-based)

• Storage Options: Amazon S3, local NAS, Dropbox, Wasabi, etc.
• BYOS? ✅ Fully
• Why it’s good:
  • Has built-in multi-location storage handling
  • Strong support for bulk metadata operations
  • Interface is mature and searchable
• Scale: 30–100+ TB with proper tuning
• Cost: Free (self-hosted), cloud plan available

🔧 Best for: Organizations needing multi-site or distributed archive setups.

⚠️ Honorable Mentions (with limitations):

🔍 Bottom Line

If you’re handling 30–40 TB of archival content for a museum or library, your best BYOS options are:

Let me know:

• what kind of assets (images, videos, scans?)
• what kind of access (internal only or public-facing?)
• and whether you want local, cloud, or hybrid storage—

…and I can give you a more tailored shortlist.

Thanks — that narrows things down very usefully.

You’re looking for a BYOS-friendly Digital Asset Management System that meets these criteria:

📦 Primary Needs:

• Handles large TIFF images (ideally >100MB+)
• Auto-generates JPG derivatives for fast viewing
• Offers internal + public-facing access
• Requires minimal IT setup (cloud or managed hosting)
• Budget: under $25,000/year
• Supports BYOS: i.e., integrates with Google Drive, Amazon S3, or similar cloud storage

✅ Top 2 Recommendations (Best Fit for Budget + Features)

1. Pics.io

🟢 Best Option for Cloud, BYOS, TIFFs, and Portals

• BYOS? Yes: Google Drive, Amazon S3, or Wasabi
• TIFF support? Yes (full-resolution support + automatic JPG derivatives)
• Public Portals? Yes — create customizable, branded portals for public access
• Internal Access? Role-based permissions, multiple users
• Metadata Support? Rich custom fields, CSV import/export, IPTC/XMP reading
• Search? Excellent — tags, custom fields, nested folders, filters

💰 Pricing Estimate (subject to plan updates):

• ~$150–$250/month for up to 10 users (varies by features like Portals, versioning)
• Bring your own storage = zero cost for bandwidth
• Add Amazon S3 or Wasabi (~$5/TB/month) for scalable TIFF storage
• Easily stays under $10,000–15,000/year total

🧠 No IT staff needed: Fully managed SaaS; you control storage via your own Google or S3 bucket

🌐 https://pics.io

2. Razuna (Cloud Hosted Version)

🟢 Affordable, BYOS, TIFF-friendly

• BYOS? Yes — connect to S3, Wasabi, Google Drive
• TIFF Support? Yes — can generate JPG previews automatically
• Public Portals? Yes, via “collections” shared publicly
• Internal Use? Multi-user support, tags, categories, custom metadata
• Search? Tag-based, category, filename, metadata

💰 Pricing Estimate:

• Cloud-hosted plans from $200–$400/month
• BYOS via S3 or Wasabi (~$2–5/TB/month) = scalable and budget-friendly
• Stays under $20,000/year, depending on usage tier

🌐 https://razuna.com

🟡 Honorable Mentions (Require Setup or Custom Hosting)

🧮 Estimated Annual Cost (Example for Pics.io + Wasabi):

That’s well under your $25k budget, with plenty of margin for support, consulting, or expanding to more users.

🟢 Recommendation Summary:

Would you like:

• A step-by-step trial setup guide for Pics.io with Wasabi or Google Drive?
• A sample public portal layout for your archive?
• Help planning metadata imports (e.g. bulk TIFF → JPG → CSV import)?

Let me know, and I’ll walk you through the full setup.

Here’s your comprehensive guide on using Pics.io for a large historical photo archive (~30‑40 TB of TIFFs), powered either by Wasabi or Google Drive storage:

1. Setup Guide: Trialing Pics.io with Wasabi & Google Drive

🧪 With Wasabi S3

1. Register for a Pics.io account and start your free 7-day trial—no credit card required. (Pics.io - DAM insights and news, Pics.io - DAM insights and news)
2. On the “Choose Storage” screen, select Amazon S3 / Wasabi.
3. Enter AWS‑compatible credentials (access key and secret key). Pics.io treats Wasabi as S3 storage. (Reddit)
4. Select or create a bucket where your TIFF assets live or will reside. Pics.io will index and reference them—no migration needed. (Pics.io - DAM insights and news)
5. Once synchronized, Pics.io will generate JPG previews for each TIFF—ideal for browsing.
6. Invite users, create metadata fields, import via CSV, and configure public or internal portals.

🧪 With Google Drive

1. Register and start your trial.
2. Choose Google Drive on setup. Grant access via the Drive Marketplace app if prompted. (workspace.google.com, Pics.io - DAM insights and news)
3. Specify a root Pics.io folder or let the system create one (e.g. Pics.io).
4. Upload your TIFFs into that folder (via Drive Sync, upload, or Backup & Sync).
5. Use the Sync feature in Pics.io to detect and index all assets. (Pics.io - DAM insights and news, Pics.io - DAM insights and news)
6. Pics.io will auto-create JPG derivatives for previews, and watch for new additions automatically.

2. 🎨 Sample Public Portal Layout

Here’s a clean design mockup for a public-facing archive portal:

• Home Page: Hero banner + introduction to your museum’s photo archive
• Filter Sidebar:
  • Date Taken (range selector)
  • Subject Keywords
  • Photographer / Creator
  • Archive Collection
  • Rights Status
• Main Gallery:
  • Grid of JPG previews (50+ thumbnails/page)
  • Hover reveals metadata summary (title, date, location)
• Asset Detail Overlay:
  • Larger image view
  • Metadata panel (caption, accession #, negative #, description, rights, location)
  • “Download high-res TIFF” link for public assets
• Footer: About, Contact, Terms / Usage Rights

Navigation menus and search box allow quick browsing. Portals are fully branded and customizable via Pics.io. All built-in.

3. 📥 Planning Metadata Imports & Workflow

Workflow Overview

1. Organize TIFFs and upload to Wasabi bucket or Drive folder.
2. Create CSV with metadata (see template previously provided).
3. In Pics.io, define Custom Fields matching your CSV headers (e.g. Accession Number, Date Taken, Collection).
4. Use Import → CSV function to batch import metadata while preserving attachments.
5. New orders processed, and JPG derivatives generated automatically.
6. Organize assets into Collections (e.g. by year, photographer), and configure which Collections become public portals.

Cost Estimate

• Pics.io Pro Plan: ~$150–250/mo for metadata, versioning, portals, etc. (selecthub.com, Reddit)
• Wasabi Storage: ~$6/TB/month; 40 TB ≈ $2,400/year (plus retention considerations) (Reddit)
• Google Drive: Depending on Workspace storage. Free if available.
• Total Annual Cost: Pics.io plus Wasabi = ~$5K–$7K/year, well under your $25K budget.

4. 🚀 What It Looks Like: Using Pics.io for Your Museum Archive

A. Narrative Workflow

Initial Setup

You sign up, choose storage (Wasabi or Drive), connect a bucket or folder, and in minutes your TIFF files are indexed into Pics.io. Previews and metadata setup begins immediately.

Metadata & Cataloging

Using defined custom fields (Accession #, Date, Photographer, Format, Rights, Negative Number, etc.), you batch import via CSV and clean up metadata in bulk. Tags and controlled values ensure consistency.

Browsing & Internal Use

Staff log in to the Pics.io backend to search by keywords, dates, or metadata, view previews quickly, add comments, and refine metadata. Version control helps track edits or updated scans.

Public Interface & Sharing

You publish Collections (e.g., “Paris Street Portraits 1930s”) as branded public portals. Visitors can filter, browse, view, and optionally download full TIFFs if rights allow.

Maintenance

Continue syncing new assets (via Drive Sync or upload to S3). Pics.io automatically indexes them. Publish new Collections as needed, or close previous ones. Full audit logs track updates.

B. Key Features & Benefits (Outline)

✅ Summary

• Pics.io with Wasabi: Strongest match for your needs—scalable, low-cost, easy to manage, handles TIFFs, creates JPG derivatives, and supports both internal and external use.
• Pics.io with Google Drive: If you already have Drive storage capacities, or prefer Google Workspace, this is a no-setup option and equally supported.
• Either setup can scale to 30–40 TB and stay well under your $25K annual budget.
• Metadata import, search, portal publishing, and asset linking are well-supported through intuitive UI.

Would you like me to generate a full CSV import template based on your custom field spec? Or mockup a portal homepage layout with real asset examples? Just let me know!

Great! Here’s the detailed deliverable for each of your requests:

1. CSV Import Template for Pics.io (Custom Fields)

This CSV template includes fields relevant to a large museum archive of historical photographs, built to match Pics.io’s import requirements and common archival metadata:

Notes:

• filename: The exact file name of the TIFF stored on your Wasabi/S3 or Google Drive.
• title: Short descriptive title.
• description: Longer text describing the photo, context, or subject.
• date_taken: ISO date format (YYYY-MM-DD).
• photographer: Creator or photographer name.
• location: Place where photo was taken.
• collection: Your internal collection grouping (used for portals).
• accession_number: Your museum’s unique identifier.
• negative_number: Identifier for the original negative (if applicable).
• rights: Usage rights info.
• format: File format (TIFF, JPEG, etc.).
• keywords: Comma-separated searchable keywords.
• source: Provenance or source of the asset.

2. Mockup of Portal Homepage Layout for Historical Photo Archive

------------------------------------------------------
| [Museum Logo]    Historical Photo Archive          |
------------------------------------------------------
| Search bar: [_________________________] [Search]   |
------------------------------------------------------
| Filters Sidebar:                                     |
|  - Date Taken: [1920 - 1950]                        |
|  - Photographer: [Dropdown list]                    |
|  - Location: [Dropdown list]                         |
|  - Collection: [Paris Street Portraits, Artists...] |
|  - Rights: [Public domain, Creative Commons, etc.]  |
------------------------------------------------------
| Main Gallery:                                       |
| [Thumbnail: Eiffel Tower 1920] [Louvre Courtyard]  |
| [Thumbnail: Montmartre Artist 1940] [Next→]        |
------------------------------------------------------
| Footer: About | Contact | Terms & Usage            |
------------------------------------------------------

• Thumbnail views show JPG previews automatically generated from TIFFs.
• Clicking a thumbnail opens the asset detail page with full metadata and a “Download TIFF” option (if public).
• The portal is branded with your museum’s colors and logo, customizable via Pics.io.
• Visitors can filter by date, photographer, location, rights, or search by keywords.

3. Pricing Comparison Chart: Google Cloud Storage vs Amazon S3 vs Wasabi (40–60 TB scale)

Summary:

If you want, I can generate:

• A real CSV file ready for import (with dummy example data).
• A visual mockup image or clickable prototype for the portal homepage.
• A more detailed cost breakdown including transfer and API request estimates.

Let me know which next step you want!