Frequently asked questions and handy info Reference page

Last updated: 13 July 2026

Mimic Labs exists to make tools that people can understand, repair, customize, and build upon.

We do not believe buying a product should mean surrendering control over it. Owners should be able to inspect how their tools work, replace damaged components, modify their hardware, change their firmware, and keep the product useful long after its original release.

At the same time, making source files available should not automatically give another company permission to reproduce the complete product, remove the original creator from the story, and sell the result as its own.

This page explains how Mimic Labs handles product licensing, personal fabrication, repairability, source releases, compatible modules, community contributions, official certification, manufacturing, creator compensation, branding, and safety.

The exact license files distributed with a product control its legal use. This page is intended to explain those terms in plain language and describe the additional policies used by Mimic Labs.

Can I repair a Mimic Labs product?

Yes.

Owners may open, maintain, modify, and repair their products. Released source files may also be used for personal repairs within the terms of the applicable license. it is yours, this is how it should be.

We aim to provide useful repair information rather than treating disassembly as misuse.

Can I modify my product?

Yes.

You may modify the physical hardware, firmware, software configuration, case, controls, modules, and other owner-accessible parts of your product.

A modified product may no longer be covered by the original warranty when the modification caused or contributed to the failure, but opening or modifying a product does not automatically erase support for unrelated problems.

Can I build the Dungeon Delver myself?

Yes, for personal and noncommercial use. its source package will be slightly delayed after released.

The applicable product page will identify which files are available and the license covering them.

Can another company sell Dungeon Delver keyboards or kits?

Not without a separate commercial agreement from Mimic Labs.

The community release is intended to support personal fabrication, repair, study, modification, and experimentation. It is not permission for another company to manufacture competing Dungeon Delver keyboards, kits, covered components, or commercial derivatives from the released core design.

Can someone design and sell modules for the Dungeon Delver?

Yes.

Independent creators may design and sell compatible modules. Official Mimic Labs approval is not required merely to create something compatible with a published interface.

Modules based on Mimic Labs open module source must follow the license covering that source. Modules seeking Mimic Certified status, official promotion, manufacturing, consignment, or store placement must also meet the open-source and documentation requirements described below.

Do community modules have to be open-source?

Mimic Labs strongly encourages every compatible module to be open-source and repairable.

A genuinely independent design does not automatically become subject to a Mimic Labs license merely because it is compatible with the Dungeon Delver.

However, open-source release is required for official Mimic Labs recognition, including Mimic Certified status, official registry placement, Mimic Labs manufacturing, consignment, promotion, or store placement.

Can I resell a product I bought?

Yes.

Mimic Labs does not object to the ordinary resale, gifting, or transfer of a physical product you lawfully own.

That is different from manufacturing products with the intention of selling them.

Product-Specific Licensing

Mimic Labs does not place every type of work under one blanket license.

Hardware, firmware, software, documentation, interface specifications, artwork, and branding have different requirements and may use different licenses.

Each applicable product page and source repository will identify:

  • the hardware-design license;

  • the firmware or software license;

  • the documentation license;

  • the current source-release status;

  • any additional permissions;

  • any excluded components or files;

  • the applicable license version;

  • the official source location.

When this plain-language policy conflicts with an actual license distributed with a project, the actual license controls.

A license applied to one product or component does not automatically apply to every Mimic Labs product.

Core Mimic Labs Products

Core products such as the Dungeon Delver may have their mechanical and electronic design files released under:

Open Community License v1.1 with General Attribution v1
OCL v1.1 + GAtt v1

This is a community-open license intended to provide meaningful access to the product while reserving commercial reproduction rights.

For a noncommercial end user, OCL permits use, copying, modification, and experimentation with the covered product and its covered components.

When a noncommercial user distributes a derivative based on OCL-covered material:

  • the derivative must remain under OCL;

  • the applicable OCL add-ons must remain attached;

  • required creator identification must be retained;

  • the derivative must not be presented as an official Mimic Labs product unless separately approved.

The General Attribution add-on requires reasonable identification of the creators whose work the derivative is based upon.

For commercial business users, OCL permits internal use and modification but does not permit commercial reproduction or sale of the covered product, covered components, or derivatives without a separate business or repair license.

For the Dungeon Delver, this means the public release of core design files does not authorize another business to sell:

  • complete Dungeon Delver keyboards;

  • Dungeon Delver kits;

  • commercial reproductions;

  • modified commercial clones;

  • covered core assemblies;

  • collections of covered parts intended to function as a competing kit;

  • covered replacement parts as a commercial product line unless separately permitted.

Only the files and components specifically identified as OCL-covered are subject to OCL.

The module interface, reference module designs, firmware, documentation, artwork, and branding may use different licenses.

Personal Fabrication Permission

OCL does not clearly address every situation where an individual hires a commercial fabrication service to produce a personal, noncommercial build.

Where specifically listed on a product page or included with a source release, Mimic Labs therefore grants the following additional permission:

Mimic Labs Personal Fabrication Permission v1.0:

A noncommercial individual may provide the covered manufacturing files to a third-party fabrication or assembly service solely to produce a personal-use build or personal-use replacement parts for that individual.

The fabrication service may charge for its materials, machine time, labor, shipping, and ordinary service costs.

This permission does not grant the fabrication service any right to:

  • manufacture additional units;

  • retain the files for unrelated future use;

  • reuse the design for another customer;

  • redistribute the files;

  • publish the files;

  • advertise the covered design as one of its own products;

  • maintain commercial inventory;

  • offer the covered product in a catalog;

  • sell extra units or overruns;

  • sublicense the design;

  • claim partnership with Mimic Labs;

  • use Mimic Labs branding;

  • use the Dungeon Delver name as the service’s own product name.

The service may retain files temporarily when reasonably necessary to complete the individual order, maintain legally required business records, or resolve manufacturing defects related to that order.

This permission does not authorize:

  • commercial production;

  • group buys;

  • crowdfunding campaigns;

  • dealer activity;

  • repeated production runs;

  • manufacturing for resale;

  • inventory building;

  • selling kits;

  • selling unfinished collections of parts intended to avoid the complete-product restriction.

A person may not claim that a commercial order is personal fabrication when the quantity, frequency, promotion, organization, or surrounding activity reasonably indicates production for resale or commercial distribution.

Mimic Labs may provide separate written permission for educational programs, accessibility needs, nonprofit workshops, repair organizations, research groups, or other special circumstances.

This additional permission applies only where a product page or source release explicitly says that it applies.

Personal Builds and Official Products

A personally fabricated product is not an official Mimic Labs-manufactured product.

Personal and community builds are not automatically covered by Mimic Labs:

  • manufacturing quality control;

  • factory testing;

  • assembly verification;

  • warranty coverage;

  • safety certification;

  • serial registration;

  • customer support; (Though we will still try to help if needed!)

  • replacement programs;

  • official product claims.

This does not make a personal build illegitimate. It simply means Mimic Labs cannot warrant manufacturing work it did not perform or supervise.

A person may accurately describe their build as:

  • built from released Dungeon Delver source;

  • based on the Dungeon Delver design;

  • compatible with the Dungeon Delver ecosystem;

  • a personal or community-built Dungeon Delver.

They may not describe it as manufactured, certified, inspected, warrantied, or officially approved by Mimic Labs unless that is true.

Repairability

Repairability is a design requirement, not a marketing label.

Where reasonably practical, Mimic Labs intends to provide:

  • disassembly information;

  • replaceable fasteners;

  • connector documentation;

  • wiring information;

  • firmware access;

  • replaceable wear components;

  • replacement-part information;

  • diagnostic guidance;

  • repair documentation;

  • component identification;

  • source files for released repairable components.

Owners may use released files to make personal replacement parts and repair their own products.

Businesses may use OCL-covered material for internal repair of products owned and used by that business, as permitted by OCL.

A commercial repair service that manufactures OCL-covered replacement components for customers may require a separate repair license or written permission.

Mimic Labs may release selected service parts under a more permissive or commercially usable license when broader repair-part availability would better support long-term ownership.

A product page or source repository may identify a component as an:

Open Repair Part

Open Repair Parts may be commercially manufactured and distributed under the license identified with that part, provided the applicable source, attribution, and notice requirements are followed.

Open Modules and Expansion Hardware

Hardware intended to support community development and commercial module sales may be released under:

CERN Open Hardware Licence Version 2 — Strongly Reciprocal
CERN-OHL-S-2.0

This license permits people and businesses to:

  • study the covered source;

  • modify the design;

  • make products from it;

  • distribute the source;

  • distribute physical products;

  • sell physical products.

When a product based on CERN-OHL-S-2.0 source is distributed, the recipient must receive the Complete Source or be clearly directed to a lasting Source Location containing it.

Covered modifications must remain under the applicable reciprocal license terms.

This is the intended licensing model for:

  • module reference designs;

  • module templates;

  • open accessories;

  • expansion hardware;

  • community modules intended for commercial sale;

  • selected repair components;

  • other hardware intended to remain commercially usable and open.

Creators are allowed to make money from open hardware.

Selling an open-source module does not violate the purpose of the ecosystem. Closing the design after using reciprocal community source does.

The Dungeon Delver Interface

Mimic Labs intends to publish the technical information reasonably necessary to develop compatible modules.

This may include:

  • mechanical envelopes;

  • attachment geometry;

  • connector positions;

  • pogo-pin locations;

  • voltage limits;

  • current limits;

  • communication protocols;

  • addressing requirements;

  • power behavior;

  • firmware expectations;

  • identification behavior;

  • safety requirements;

  • compatibility constraints.

The written interface specification may use a permissive documentation license such as CC BY 4.0, as identified on the applicable release.

Publishing an interface permits independent compatibility. It does not give Mimic Labs ownership over every independently developed compatible device.

It also does not grant permission to use Mimic Labs trademarks, certification marks, artwork, packaging, or other protected brand material.

Independently Created Compatible Modules

A compatible module does not need to be submitted to Mimic Labs merely to exist.

Creators are welcome to experiment with:

  • input devices;

  • pointing devices;

  • displays;

  • controls;

  • sensors;

  • accessibility tools;

  • artistic modules;

  • productivity modules;

  • unusual or highly specialized hardware;

  • ideas Mimic Labs would never have considered.

A module that incorporates, modifies, or derives from licensed Mimic Labs source must follow the license covering that source.

A module created independently without incorporating licensed Mimic Labs source remains governed by the rights and license selected by its creator.

Mimic Labs asks independent creators to keep compatible modules open-source because closed modules weaken repairability and long-term user control.

However, compatibility alone does not automatically create a copyright license obligation where no protected source was incorporated.

Official Mimic Labs recognition does create additional requirements.

Requirements for Officially Recognized Modules

A module must be openly documented and released under an approved reciprocal license to receive official Mimic Labs recognition.

This includes:

  • Mimic Certified status;

  • an official compatibility badge;

  • official registry placement;

  • Mimic Labs promotion;

  • Mimic Labs manufacturing;

  • consignment;

  • store placement;

  • official packaging;

  • sale through Mimic Labs.

The preferred hardware license is CERN-OHL-S-2.0.

Another reciprocal open-hardware license may be accepted when Mimic Labs determines that it provides equivalent source, modification, manufacturing, repair, and reciprocity rights.

Officially recognized modules must provide the source material reasonably necessary to understand, manufacture, modify, maintain, and repair the product.

Depending on the module, this may include:

  • native schematic files;

  • native PCB-layout files;

  • mechanical CAD;

  • editable assembly files;

  • STEP or other broadly readable mechanical exports;

  • PDF schematics;

  • manufacturing outputs;

  • firmware source;

  • bootloader or flashing information;

  • configuration files;

  • a bill of materials;

  • component specifications;

  • assembly instructions;

  • wiring information;

  • connector information;

  • programming instructions;

  • test procedures;

  • calibration procedures;

  • required license notices;

  • attribution information;

  • revision history;

  • safety information;

  • known limitations;

  • a stable public source repository.

Gerbers, STL files, screenshots, compiled firmware, PDFs, or other output files alone may not qualify as complete source when editable source files exist.

Proprietary native files may be accepted, but reasonable neutral or broadly readable exports should also be provided where possible.

Firmware and Software

Firmware and software are licensed separately from hardware.

QMK-based Dungeon Delver firmware is expected to be released under:

GNU General Public License, version 2 or later
GPL-2.0-or-later

This matches the licensing requirements of QMK firmware.

Distributed QMK-based firmware must be accompanied by the applicable corresponding source as required by the license. Shipping only a compiled firmware binary is not sufficient.

Other firmware or local software may use:

  • GPL-2.0-or-later;

  • GPLv3;

  • another compatible reciprocal software license identified with the project.

Hosted configurators, server-side tools, registries, and network-accessible software may use AGPLv3 or another identified license when keeping hosted modifications open is important to the project.

The exact license included with the software controls.

Hardware licensing does not override software licensing, and software licensing does not automatically license the physical hardware.

Technical Documentation

Technical documentation may be released under:

Creative Commons Attribution-ShareAlike 4.0 International
CC BY-SA 4.0

This permits documentation to be:

  • copied;

  • redistributed;

  • translated;

  • reformatted;

  • adapted;

  • improved;

  • used commercially.

Appropriate credit must be provided, changes must be identified, and adapted material must remain under the same or a compatible share-alike license.

This may apply to:

  • assembly guides;

  • repair manuals;

  • build instructions;

  • wiring diagrams;

  • technical illustrations;

  • educational explanations;

  • compatibility documentation;

  • manufacturing notes;

  • calibration guides;

  • troubleshooting information.

CC BY-SA 4.0 does not automatically apply to artwork, branding, marketing material, characters, product renders, packaging, or other assets that are not explicitly identified as licensed documentation.

What Mimic Labs Means by “Open Source”

The phrase “open source” has a specific established meaning.

Formal open-source hardware permits anyone to study, modify, distribute, make, and sell hardware based on the released design.

Because OCL restricts commercial reproduction, an OCL-covered core product does not meet that formal definition.

Mimic Labs may therefore describe OCL-covered hardware as:

  • community-open;

  • source-available;

  • user-fabricable;

  • publicly documented;

  • repairable by design.

Hardware released under CERN-OHL-S-2.0 may be described as open-source hardware.

Firmware released under GPL terms may be described as open-source software.

We will not use one broad label to hide meaningful differences between the licenses.

The license identified with the work matters more than the marketing term used to summarize it.

Source Release Timing

Some Mimic Labs source packages may be released after an initial product-launch stabilization period.

For the Dungeon Delver, the current plan is to release the applicable public source package approximately 90 days after the first production shipments.

This period exists to:

  • collect early customer feedback;

  • identify production issues;

  • release hot-fixes;

  • stabilize revisions;

  • correct documentation;

  • verify manufacturing files;

  • improve build instructions;

  • prepare repair resources;

  • confirm source-license notices;

  • make the public release genuinely usable.

The purpose is not to sell customers an inferior or intentionally restricted product.

The initial production period gives Mimic Labs time to make sure the public source package corresponds to a stable production revision rather than publishing unfinished files that immediately become misleading or obsolete.

The applicable product page will identify:

  • whether source has been released;

  • the planned release window;

  • the released revision;

  • the source repository;

  • the applicable licenses;

  • known differences from later revisions.

A release target is a good-faith plan, not a promise that unsafe, incomplete, legally conflicting, or third-party-restricted material will be published unchanged.

When something cannot be released, Mimic Labs will identify the exclusion rather than quietly pretending the source package is complete.

Official Mimic Labs Approval

Official approval is optional.

A community-made module may exist, be published, and be sold without Mimic Labs approval, provided it does not misuse Mimic Labs source, licenses, trademarks, or certification claims.

Official approval means Mimic Labs has reviewed a specific revision for a specific form of recognition.

Review may include:

  • electrical safety;

  • voltage behavior;

  • current draw;

  • connector behavior;

  • communication behavior;

  • firmware behavior;

  • mechanical fit;

  • user safety;

  • documentation quality;

  • source completeness;

  • license compliance;

  • manufacturing readiness;

  • repairability;

  • reliability;

  • quality-control requirements;

  • customer-support burden;

  • compatibility claims;

  • branding clarity.

Approval does not mean the creator gives up authorship or ownership.

The original creator remains credited unless a separate written agreement says otherwise.

Approval applies only to the reviewed revision. Material design, component, firmware, manufacturing, or safety changes may require renewed review.

Mimic Certified

Approved modules may qualify for the Mimic Certified program.

A certified module may receive:

  • an official certification badge;

  • a certification record;

  • a unique record or serial identifier;

  • registry placement;

  • approved compatibility claims;

  • access to official Mimic Labs channels;

  • eligibility for manufacturing or consignment discussions.

The registry may include:

  • product name;

  • product description;

  • creator or author;

  • license;

  • certification status;

  • approval date;

  • certification number;

  • hardware revision;

  • firmware revision;

  • supported products;

  • source-repository location;

  • manufacturing status;

  • known limitations;

  • warnings;

  • certification history.

Certification does not mean Mimic Labs owns the module.

It means Mimic Labs reviewed the identified revision and found that it met the requirements in effect at the time of review.

Certification may be suspended or withdrawn when:

  • an undisclosed revision is sold;

  • source availability is removed;

  • license obligations are violated;

  • safety or reliability problems are discovered;

  • certification marks are misused;

  • compatibility claims become inaccurate;

  • required documentation is not maintained.

Previously granted open-source rights remain governed by the applicable license even when certification status changes.

Naming and Branding of Community Modules

Creators may choose their own project names.

Mimic Labs may request a different product name for official certification, packaging, store placement, or promotion when the proposed name creates:

  • trademark concerns;

  • customer confusion;

  • unclear product organization;

  • false official-status implications;

  • safety confusion;

  • inappropriate compatibility claims;

  • conflict with established Mimic Labs product naming.

A requested official name change does not transfer ownership of the creator’s underlying design.

Creators may continue using their own name outside official Mimic Labs channels when doing so is lawful and does not falsely imply official status.

Community, Certified, and Official Products

Community-Made

A community-made product was created independently by a community member and has not necessarily been reviewed by Mimic Labs.

Mimic Certified

A Mimic Certified product was reviewed by Mimic Labs and approved for the certification status identified in the registry.

Official Mimic Labs Product

An official Mimic Labs product is designed, manufactured, commissioned, distributed, or formally adopted by Mimic Labs.

Consignment Product

A consignment product is an approved creator-owned product sold through Mimic Labs under a separate agreement.

Mimic-Manufactured Community Product

A Mimic-manufactured community product is a creator-designed product manufactured or assembled by Mimic Labs under a separate agreement.

Not every good module needs to become certified or official.

Some projects should remain experimental, strange, niche, personal, artistic, or chaotic. That freedom is part of the purpose of the ecosystem.

Consignment and Manufacturing

Some approved modules may be eligible for:

  • consignment;

  • official manufacturing;

  • assembly;

  • packaging;

  • distribution;

  • store placement;

  • promotion through Mimic Labs.

These arrangements are optional and require a separate written agreement.

The agreement should identify:

  • ownership of the design;

  • the license applied to the public source;

  • commercial permissions;

  • manufacturing responsibilities;

  • quality-control responsibilities;

  • inventory ownership;

  • pricing;

  • direct costs;

  • profit-share calculation;

  • reporting frequency;

  • payment frequency;

  • return handling;

  • warranty responsibility;

  • support responsibility;

  • revision control;

  • termination rights;

  • treatment of remaining inventory.

Open-source licensing does not eliminate creator ownership or compensation.

A module can remain open-source while its creator is paid for design work, products, manufacturing participation, support, or official sales.

Creator Profit Sharing

Depending on the module and arrangement, Mimic Labs may offer creators up to 50% of net profit from official sales.

The highest share is most likely when the creator provides a product that is:

  • complete;

  • documented;

  • tested;

  • safe;

  • manufacturable;

  • source-complete;

  • ready for production;

  • low in support burden;

  • low in warranty risk;

  • unlikely to require substantial redesign.

A lower share may apply when Mimic Labs must provide significant:

  • engineering;

  • redesign;

  • prototyping;

  • sourcing;

  • manufacturing setup;

  • test development;

  • certification work;

  • documentation;

  • packaging;

  • customer support;

  • warranty coverage;

  • inventory financing;

  • production risk.

The exact percentage and calculation must be agreed in writing before commercial sale.

“Up to 50%” is not a promise that every submitted idea automatically receives half of the sale price or half of the profit.

What “Net Profit” Means

Profit sharing is based on net profit, not total sale price or gross revenue.

Depending on the arrangement, direct and agreed costs may include:

  • components;

  • PCB fabrication;

  • mechanical fabrication;

  • assembly;

  • labor;

  • testing;

  • rejected units;

  • failed units;

  • packaging;

  • labels;

  • payment-processing fees;

  • marketplace or platform fees;

  • shipping materials;

  • import costs;

  • duties;

  • warranty reserves;

  • returns;

  • customer support;

  • certification work;

  • documentation work;

  • manufacturing preparation;

  • agreed redesign work;

  • applicable transaction-related taxes or fees.

Mimic Labs will not use an undefined “net profit” label as permission to invent deductions after the product begins selling.

Before launch, the creator agreement should identify:

  • which cost categories may be deducted;

  • how shared costs are allocated;

  • the agreed creator percentage;

  • how often sales are reported;

  • how often payments are issued;

  • how returns and warranty costs are handled.

The purpose is a transparent and mutually beneficial relationship, not a vague promise that cannot be audited or understood.

Safety and Quality Assurance

Mimic Labs may reject, delay, limit, or withdraw approval when a product creates concerns involving:

  • electrical safety;

  • excessive power consumption;

  • connector damage;

  • overheating;

  • battery safety;

  • mechanical hazards;

  • pinch hazards;

  • sharp edges;

  • firmware instability;

  • data or device-security risks;

  • unreliable identification;

  • unclear instructions;

  • missing warnings;

  • poor repairability;

  • incomplete source;

  • license conflicts;

  • excessive warranty risk;

  • misleading claims.

This is not intended to block experimentation.

Experimental modules are welcome, but experimental products should be clearly identified as experimental.

Community-built, modified, and experimental products are used at the builder’s own risk and are not automatically tested, certified, warrantied, or endorsed by Mimic Labs.

Mimic Labs certification is not a substitute for legally required regulatory testing or certification.

Creators remain responsible for determining which legal, safety, electrical, radio, battery, consumer-product, or other requirements apply to their products.

Warranty and Modifications

Official Mimic Labs products are covered by the warranty terms identified at the time of sale.

Opening, maintaining, or modifying a product does not automatically cancel every form of support.

However, Mimic Labs may decline warranty coverage for damage caused by:

  • incorrect assembly;

  • incompatible parts;

  • electrical overstress;

  • improper firmware;

  • unauthorized power modifications;

  • physical modification;

  • improper repair;

  • misuse;

  • neglect;

  • an unapproved module;

  • a third-party component.

Where possible, Mimic Labs will distinguish between a failure caused by a modification and an unrelated manufacturing defect.

Community-fabricated products, third-party modules, and unofficial builds are not covered by Mimic Labs warranty unless a separate written policy expressly says otherwise.

Branding, Artwork, and Official Status

Open hardware and community-open source files do not include permission to use the Mimic Labs identity.

Unless expressly identified otherwise, the following remain all rights reserved:

  • the Mimic Labs name;

  • the Mimic Labs logo;

  • the Dungeon Delver name;

  • product names;

  • Mimic Certified marks;

  • compatibility badges;

  • certification labels;

  • serial-mark graphics;

  • mascots;

  • characters;

  • lore;

  • stories;

  • worldbuilding material;

  • artwork;

  • illustrations;

  • product renders;

  • marketing images;

  • icons;

  • visual identity;

  • packaging artwork;

  • website-design assets;

  • promotional material.

You may accurately state that an independent product is “compatible with the Dungeon Delver” when the statement is truthful and does not imply manufacture, certification, sponsorship, endorsement, or partnership.

You may not describe a product as:

  • official;

  • Mimic Certified;

  • approved by Mimic Labs;

  • manufactured by Mimic Labs;

  • partnered with Mimic Labs;

  • warrantied by Mimic Labs;

unless that statement is true and authorized.

Artwork, Data Mining, and Machine Learning

Mimic Labs does not grant permission to use its reserved artwork, characters, renders, branding, visual identity, private files, or unreleased work for machine-learning training, dataset creation, automated scraping, or similar uses without express written authorization.

OCL-covered materials are also subject to the text-and-data-mining provisions contained in OCL.

Materials released under CERN-OHL, GPL, AGPL, or Creative Commons licenses remain governed by those licenses. This page does not secretly add restrictions that conflict with an applicable public license.

Where a public license permits a use, the license controls.

Where an asset remains all rights reserved, no additional permission should be assumed.

Private and Unreleased Material

Public licensing applies only to material Mimic Labs has deliberately released under an identified license.

The following are not publicly licensed merely because related products or files are public:

  • unpublished prototypes;

  • internal development files;

  • supplier information;

  • contracts;

  • customer records;

  • private quality records;

  • unreleased revisions;

  • internal pricing;

  • security credentials;

  • manufacturing secrets not included in a release;

  • private communications;

  • confidential partner material;

  • third-party material Mimic Labs does not own.

A public release does not grant rights to unrelated private files.

Policy and License Updates

Mimic Labs may update this explanatory policy as products, programs, and licensing practices evolve.

Each source release will identify the specific license and version applied to that release.

A future policy update does not silently replace the license file included with an earlier source release.

When a project moves to a later license version, the repository or product page will identify which version applies.

Mimic Labs may correct errors, clarify wording, add examples, and improve program requirements as practical experience develops.

When a meaningful policy change affects creators, customers, certification, or source access, we will make a reasonable effort to identify the change clearly.

Our Intent

The goal is to create an ecosystem that remains understandable, repairable, expandable, and economically fair.

We want owners to control their tools.

We want people to build personal versions.

We want people to repair products instead of discarding them.

We want creators to design modules we never would have imagined.

We want creators to receive credit.

We want community members to be able to sell their own open designs.

We want good community work to have a path toward certification, manufacturing, promotion, and revenue.

We also need Mimic Labs to remain capable of funding the engineering, testing, documentation, support, and manufacturing required to build the core products in the first place.

That balance is why different parts of the ecosystem use different licenses.

The Dungeon Delver core is community-open and personally fabricable, while commercial reproduction remains reserved.

The module ecosystem is intended to be genuinely open-source and commercially usable.

Firmware remains inspectable and modifiable.

Documentation remains shareable and improvable.

Branding remains protected so people can tell what is official and what is independent.

Transparency does not require abandoning the right to operate a sustainable company.

Protection does not require taking control away from the people who own the product.

Links and References

Here are links to all licenses mentioned for reference if needed: