Enterprise DNA

Instead of MyApiary

Stop renting MyApiary. Own your apiary records.

We build your version around your sites, teams and harvest routines. We map your MyApiary exports, reconcile your records and run your system through Omni by Enterprise DNA.

MyApiary Manager Commercial lists US$999 per user a year, excluding taxes. Extraction is a separate subscription.

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

The subscription you are comparing

Separate the field tools from the records you need

MyApiary sells Manager and Extraction separately. Compare your actual contract, the field work it supports and the records you want to own. These are US prices, excluding taxes.

paid

Manager seats

Commercial is US$999 per user annually, or US$99 per user on monthly billing.

person

The smaller operation

Sideliner is US$699 annually, limited to one user and 350 hives.

layers

Multiple regions

Professional is US$1,399 per user annually and adds multiple regions and asset tracking.

inventory_2

Extraction reporting

The separate Reporting Only package is US$2,499 annually.

warehouse

Extraction operations

Extraction Commercial is US$3,999 annually. Professional is US$5,499 annually.

tablet

Field work and history

MyApiary includes field data entry and reporting. Decide which field workflow you need alongside your owned records.

What the free base does

An apiary week built from your records

Visit planning

Put the late sites first

Each site has its own visit interval. See stale observations alongside unfinished work.

  • check Site groups and landowner contacts
  • check Latest hive counts, supers and observation dates
  • check Job due dates and team assignments
  • check Change the visit interval for each site

Health records

Keep follow-ups attached to the site

Read inspection and treatment history before deciding the next job.

  • check Disease findings and notification references
  • check Treatment batch and operator instructions
  • check Removal dates and recorded harvest holds
  • check Record checks with links to NZ sources

Honey history

Trace an extraction batch to its sites

Connect harvested quantities to batch inputs and the supporting evidence.

  • check Site and harvest dates for each batch input
  • check Declaration and tutin evidence references
  • check Checks against allocating more than was harvested
  • check Private harvest preparation and batch documents

Ownership

Change the questions as your season changes

Your records stay in your database. Tailor the review to the way your team works.

  • check Recorded harvest kilograms and site costs
  • check Access agreements approaching renewal
  • check Draft landowner updates for review
  • check Custom fields and private reports for your operation

Make it yours

Design your own MyApiary replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your MyApiary 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 MyApiary 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 Apiary for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Apiary for Claude Code

Connected to your own database

Which sites need a visit this week?

S-RIDGE

Name
Rimu Ridge
Site_group
Waikato
Attention
No observation

S-RIMU

Name
Rimu North
Site_group
Waikato
Hives
48
Recorded_on
2026-08-28
Days_since_visit
38
Attention
Visit overdue

S-KOWHAI

Name
Kowhai Orchard
Site_group
Bay of Plenty
Hives
32
Recorded_on
2026-09-30
Days_since_visit
5
Attention
Within visit interval

Ask it anything

Ten questions to ask of your apiary records

These are answered by the working demo. MyApiary also offers reports and exports for custom analysis; these examples show what the free version does.

chat_bubble Which sites have missed their visit interval?
chat_bubble Which teams have overdue site jobs?
chat_bubble Which treatments still need removal?
chat_bubble Which harvests lack declaration and tutin evidence?
chat_bubble Which sites have both overdue jobs and harvest evidence gaps?
chat_bubble Which suspected disease findings lack notification evidence?
chat_bubble Which access agreements need renewal within 60 days?
chat_bubble Which sites have stale hive counts or queen notes?
chat_bubble Which harvests supplied one extraction batch?
chat_bubble Which official returns still lack receipt references?

Switching

How to switch from MyApiary

A move usually involves exporting the records MyApiary makes available, mapping them into the new database, checking the results, and running both systems while your team tests the new routine.

  1. 1

    Export your records

    Open MyApiary’s Exports area and download the Sites, Landowners and latest Site Status CSVs it documents. Check your account or ask MyApiary what else you can export, since full headers and historical exports need verification. Latest site status is a snapshot, not complete history. Earlier visits, treatments, attachments and extraction history may need separate source records. Keep the original exports.

  2. 2

    Load the records

    Map the exported columns to the fields in the new database, then run a test import before loading records for real. The import has a dry run, so you can check the proposed changes first. Once the test looks right, load the records you chose to bring across. If Enterprise DNA is handling the setup, they do the mapping and import with you.

  3. 3

    Check the test results

    Review what the test import reports, including any unsupported columns, and resolve those before loading records. Compare the counts in the source exports with the records prepared for import. Check that the mapped column names and values make sense for your business. Latest site status will not recreate earlier visits or other history that was not included in the source records.

  4. 4

    Run both systems

    Keep MyApiary and your existing field capture running while your team tests the new workflow for a short period. Compare the records you rely on, such as site details, hive counts and visit history, and note anything that needs a field or rule changed. Do not treat the new database as a replacement for field tablets or official filing systems.

  5. 5

    Switch off MyApiary

    After you have checked the imported records and your team is comfortable with the new routine, stop making new records in MyApiary. Keep the original exports and any separate history records you chose to retain. Then end your MyApiary use through the arrangements for your account. Official AFB filing stays with HiveHub or the Management Agency, not the new database.

construction

Where the real effort goes

The real work is usually deciding how your own fields and rules map to the new records, then finding and reconciling the history you want to bring across. The documented site status export is only a snapshot, so earlier visits and other history may need separate sources. If Enterprise DNA runs the installation, they handle the record mapping and import with you.

Not ready for a call?

Get your MyApiary switch plan by email

We will send you the step-by-step plan for moving your business off MyApiary, 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 the dependencies
  2. 2 Run npm test and npm run demo
  3. 3 Open it in Claude Code, Codex, OpenCode or Cursor
  4. 4 Map your MyApiary CSV headers, run a dry run and import
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your apiary fields, visit rules and job routines
  • check Your MyApiary records mapped and reconciled
  • check A field screen or different technology if you need it
  • check Hardware connections scoped and tested for your operation
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 Migration checks before your team relies on the records
  • check Access controls, backups and recovery set up
  • check Ongoing changes as your sites and team grow
Talk to Sam

Questions

Instead of MyApiary, answered

Will this be cheaper than MyApiary? expand_more

That depends on your contract and the work you want us to take on. The free base has no software licence charge. A managed version has a setup fee and a retainer. Compare the complete job, including field capture, support and migration, before deciding.

Can I bring my site history across? expand_more

MyApiary documents downloads for sites, landowners and latest site status in its Exports area. We map the column names and check the counts before importing. Latest status is a snapshot. Earlier visits, treatments, attachments and extraction history need separate source records and reconciliation.

Can our beekeepers still work on tablets? expand_more

We can build a field workflow around your team, including the screens and connections agreed for your installation. Keep your existing field capture running while the new workflow is tested with your beekeepers.

Does it file AFB returns or approve honey for sale? expand_more

No. It highlights missing evidence and prepares records for review. Official returns stay with HiveHub or the Management Agency, and harvest declarations stay with the current MPI process. Disease decisions, treatment instructions and food safety checks remain with the responsible people.

What changes when Enterprise DNA runs it? expand_more

We install your database, map the records, set up access and backups, and operate the routines agreed with your team. Your fields, site rules and reports can change with the season. You keep the database and the open-source foundation.

Bring your MyApiary bill and a typical site week

Spend 30 minutes with Sam. Look at what your beekeepers use, what you need to keep and what your own version should handle. Agree the field workflow and migration before committing to a switch.

Book a call with Sam Get the free version

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

Done paying for MyApiary?

Get your version built