Enterprise DNA

Instead of Brandkit

Stop renting Brandkit. Own your brand asset rights desk.

We build your version around your brands, permissions and campaign checks. We bring your Brandkit records across, connect your storage and run it for you.

Brandkit Enterprise starts at US$12,000 a year, with a tailored quote based on requirements. Compare your full scope before switching.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What your subscription covers

A broad platform, priced around usage

Brandkit Enterprise starts at US$12,000 a year. The paid platform combines asset management and a brand portal. Decide which work your owned version needs to carry.

folder

Stored assets and traffic

Usage includes stored files and the traffic generated by uploads, downloads and sharing.

group

Unlimited users

Brandkit lists unlimited users across its editions. Its model does not charge by seat.

palette

A designed brand portal

The Pro edition includes custom design and a custom domain. Enterprise includes those features.

language

Multiple portals and languages

Enterprise includes multiple portals and multilingual features.

verified_user

Enterprise access and location

Enterprise lists single sign-on and a nominated data region.

backup

Backup and service arrangements

Enterprise lists enterprise backup, a priority service agreement and custom contract terms.

The desk you own

Make every campaign use traceable

Permissions

Keep the evidence with the asset

Record who granted permission and the exact use their evidence covers.

  • check Keep creator credits beside permission references
  • check Record a separate permission for each channel, territory and purpose
  • check Review permissions ending in the next month
  • check Find active assets without current permission evidence

Campaigns

Check the whole planned use

Compare campaign dates and purpose with the permission before recording use.

  • check Reject planned uses outside the recorded scope
  • check Check the whole campaign period against expiry dates
  • check Keep the placement location and owner beside the image
  • check Find campaigns affected when a permission is revoked

Withdrawal

Track the follow-up to an owner

See which placements need attention and record external removal evidence.

  • check List uses of withdrawn assets
  • check Assign a follow-up and due date
  • check Keep a history of the review and confirmed removal
  • check Find problem placements without an open follow-up

Weekly review

Answer questions across the records

Bring permissions, campaign use and retention reviews together in one database.

  • check Review images containing personal information
  • check Flag missing lawful purposes and overdue retention reviews
  • check Produce a branded rights register and campaign usage sheet
  • check Compare expiring permissions by channel and territory

Make it yours

Design your own Brandkit replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Brandkit. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Brandkit replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Brandkit data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Brand Assets for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Brand Assets for Claude Code

Connected to your own database

Which permissions need a review?

Team portrait pending review

Reason
No permission recorded

Winter coast campaign

Channel
website
Territory
NZ
Ends on
2026-10-18
Reason
Permission expired

Summer growers portrait

Channel
website
Territory
AU
Ends on
2026-11-01
Reason
Permission ends within 30 days

Withdrawn partner image

Channel
website
Territory
NZ
Ends on
2026-12-19
Reason
Permission revoked

Ask it anything

Ten questions your asset records can answer

These answers come from the working demo. Your actual permission evidence and campaign rules shape the version we build for you.

chat_bubble Which live placements have an expired permission?
chat_bubble Which campaigns still use withdrawn assets?
chat_bubble Which people own overdue follow-ups?
chat_bubble Which assets have no permission history?
chat_bubble Which active assets have an unknown privacy scope?
chat_bubble Which channels have permissions ending within 30 days?
chat_bubble Which personal images need a retention review?
chat_bubble Which campaign uses exceed their recorded rights?
chat_bubble Which assets are on hold without a follow-up?
chat_bubble Which problem placements have no open asset follow-up?

Switching

How to switch from Brandkit

A move like this usually involves exporting your Brandkit metadata, testing the records in the new database, then checking permissions, files and follow-ups before you stop relying on Brandkit.

  1. 1

    Export your metadata

    Use Brandkit’s documented metadata export to get the asset records and fields you want to bring across. Brandkit documents CSV metadata exports, but check with Brandkit if you are unsure what your account allows. Original media files and written permission evidence do not come across with the metadata, so plan to move or check those separately.

  2. 2

    Test the import

    Load a test copy of the exported records before you rely on the new database. The import offers a test run, so use it to see how the records will come across. Once the test looks right, load the records. Archived records stay archived, while other imported records are held for review rather than treated as ready to use.

  3. 3

    Review the records on hold

    Check the records the import holds for review, and reconcile any issues it flags before relying on them. Identical repeat imports are skipped, while changed source rows stop the batch for reconciliation. Check the asset details against your original records, file locations and written permission evidence. A Brandkit approval flag or licence name alone is not permission to use an asset.

  4. 4

    Run both side by side

    Keep Brandkit available while you use the new database for a short period. Compare the records and follow-ups you rely on, and check that original files and written permission evidence are available where needed. Have an operator verify the actual permission and its conditions before relying on a record for a campaign. Resolve gaps before making the new database your working source.

  5. 5

    Switch off Brandkit

    Once you have checked the records, evidence, file locations and follow-up process, move the work to the new database and stop relying on Brandkit. Keep any records or history you still need according to your own retention requirements. Back up the new database and test that you can restore it before you close out your old working setup.

construction

Where the real effort goes

Most of the work is mapping your own fields and rules, then deciding which history to bring and checking that the records match your files and permission evidence. Original media and written evidence move separately from the metadata. If Enterprise DNA runs the move, they bring your Brandkit metadata across, build the agreed fields and rules, and reconcile records and storage locations as part of your custom version.

Not ready for a call?

Get your Brandkit switch plan by email

We will send you the step-by-step plan for moving your business off Brandkit, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Choose who builds and runs your version

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and install its dependencies
  2. 2 Run npm test and npm run demo
  3. 3 Open it in Claude Code, Codex, OpenCode or Cursor
  4. 4 Export Brandkit metadata, test the import and reconcile permission evidence
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your brands, fields, permission checks and campaign rules
  • check Your Brandkit records mapped and reconciled
  • check A web front end or different technology where your team needs it
  • check Your media storage and distribution connections built to the agreed scope
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Connected to your storage and the rest of your business
  • check Backups, maintenance and agreed review checks handled for you
  • check Your system changed as your campaigns and permissions change
Book a call with Sam

Questions

Instead of Brandkit, answered

Does this replace the whole Brandkit platform? expand_more

The free version covers the rights desk: asset records, permission evidence, campaign use and withdrawal follow-ups. We build the visual library, staff access, storage and distribution connections your installed version needs. We agree and test the scope before you move the work.

Can we bring our current assets across? expand_more

Brandkit documents a metadata export. The free version imports those records in one step after a test run, keeps archived records archived and holds the others for review. Original media and written permission evidence move separately. We reconcile the records and storage locations in your custom version.

Will an approved image automatically be cleared for a campaign? expand_more

No. A source approval flag or licence name is not permission evidence. The free version checks a planned use against the channel, territory, purpose and dates you have recorded. Your operator checks the actual permission and its conditions before relying on that record.

What happens when a permission is withdrawn? expand_more

The affected campaign uses appear for follow-up, with the recorded location and owner. The free version drafts an internal brief and records removal evidence supplied by the operator. It does not change public content. We build any agreed distribution controls into your installed version.

What does Enterprise DNA charge? expand_more

One setup fee, then a retainer. Sam scopes the work around your records, storage, staff access and campaign process. Your database and the system built for you remain yours. The free version is available if you want to run the rights desk yourself.

Bring the assets you are no longer sure you can use

In a 30-minute call, Sam will walk through your current bill, permission records and campaign process. You will leave with a defined scope for the version your business needs.

Book 30 minutes with Sam Get the free version

Brand Assets for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Brandkit?

Get your version built