Frequently asked questions and handy info

Open Source, Compatibility & Community Hardware Policy

Mimic Labs exists to make useful, repairable, expandable tools that people can build, modify, study, and improve.

We believe the best products are not sealed boxes. They should be understandable. They should be repairable. They should invite experimentation. When we make something, we want people to have the option to buy it from us, build it themselves, modify it, learn from it, or create something new that works with it.

This page explains how Mimic Labs handles open-source hardware, firmware, documentation, compatible expansions, official approval, and community-created modules.

The short version:

Our functional product files are open.

Our brand and art are not.

That means our hardware designs, firmware, documentation, and technical resources may be released under open licenses that allow people to study, modify, share, build, and sell compatible work.

However, the Mimic Labs name, logos, product names, badges, characters, artwork, renders, icons, and brand identity are not released for public reproduction unless we give written permission.

You are welcome to make things that work with Mimic Labs hardware. We ask that compatible expansions remain open-source so the ecosystem stays repairable, inspectable, and community-driven.

Official Mimic approval, registry listing, compatibility badges, and consignment/manufacturing opportunities require additional review.

What we release openly

Depending on the project, Mimic Labs may release:

  • PCB source files

  • schematics

  • mechanical CAD Assemblies/parts

  • enclosure files

  • module templates

  • BOMs

  • firmware

  • software tools

  • test procedures

  • assembly documentation

  • wiring diagrams

  • compatibility specifications

  • manufacturing notes

The goal is simple: if we say something is open, people should have enough source material to understand it, modify it, and build it.

What is not open

Our functional designs may be open, but our brand and creative identity are not.

The following are not open-source unless we clearly say otherwise in writing:

  • Mimic Labs logos, names, product names, and official compatibility marks

  • serial-numbered certification badges or approval marks

  • mascots, characters, lore, worldbuilding assets, and story material

  • artwork, renders, illustrations, icons, packaging art, marketing images, and visual identity assets

  • website design assets and brand presentation material

  • private business documents, supplier contracts, customer records, internal QA records, and unpublished prototypes

Artwork, characters, brand assets, visual identity, and story materials are handled separately under the Mimic Labs Artwork & Brand Use Policy and Mimic Studio Guidelines.

Until those guidelines are published, please treat those assets as all rights reserved. That means they may not be copied, reproduced, redistributed, modified, trained on, used commercially, or included in derivative works without express written permission.

The goal is not to stop people from building, modifying, or expanding Mimic Labs hardware. The goal is to keep the functional ecosystem open while keeping the Mimic Labs identity clear and protected.

Full Mimic Studio Guidelines are currently being prepared. Until then, all Mimic Studio artwork and identity assets are all rights reserved.

Why we use open licenses

Mimic Labs uses open licenses because we want people to have real access TO THE THINGS WE MAKE.

A product is not truly repairable if nobody can inspect the design. A module ecosystem is not truly expandable if nobody can understand the interface. A tool is not truly community-friendly if every improvement gets trapped behind closed doors.

Our license choices are meant to keep the functional work open while allowing Mimic Labs to sell official products, support development, and protect the brand.

Hardware license

Mimic Labs hardware source files may be released under the CERN Open Hardware Licence Version 2, Strongly Reciprocal variant, also known as CERN-OHL-S-2.0.

This license is intended for open hardware. It allows people to use, study, modify, share, distribute, make, and sell hardware based on the licensed design, while requiring modified versions of the licensed hardware source to remain open under the same license.

We use this license because it supports the kind of ecosystem we want: people can build and improve the hardware, but improvements to Mimic-based hardware designs should stay available to the community.

Firmware and software license

Mimic Labs firmware and local software tools may be released under GPLv3.

GPLv3 allows people to use, study, modify, and redistribute the software. If someone distributes modified versions or binaries based on GPLv3-covered code, they generally need to provide the corresponding source under the same license.

We use GPLv3 because keyboard firmware, module firmware, and device software should remain inspectable and modifiable.

For hosted web tools, online configurators, registries, or server-side software, Mimic Labs may use AGPLv3 instead.

AGPLv3 is similar to GPLv3, but it also helps keep modified server software open when users interact with it over a network.

Documentation license

Mimic Labs technical documentation may be released under Creative Commons Attribution-ShareAlike 4.0, also known as CC BY-SA 4.0.

This allows people to share, adapt, translate, and improve documentation, including commercially, as long as they provide attribution and keep adapted versions under compatible share-alike terms.

We use this for build guides, assembly notes, diagrams, educational material, and technical explanations.

This license does not apply to Mimic Labs artwork, branding, characters, logos, or visual identity unless we clearly say so.

Compatible expansions

Mimic Labs encourages people to create open-source expansions, modules, accessories, and modifications.

A community module does not need to be officially certified to exist. People are welcome to experiment, fork, modify, and publish their own open designs.

However, to be recognized by Mimic Labs, listed by Mimic Labs, sold through Mimic Labs, or marked with an official Mimic compatibility badge, the module must follow the Mimic Labs compatibility and review process.

Open-source expectation for compatible modules

Mimic Labs expects compatible expansions to be open-source.

At minimum, an open compatible module should include the source files needed to understand, build, modify, and repair it. This may include:

  • schematics

  • PCB source files

  • CAD files

  • firmware source

  • BOM

  • assembly notes

  • wiring notes

  • licensing information

  • safety notes

  • known limitations

We ask this because closed modules weaken the ecosystem. If a module plugs into an open platform but cannot be inspected, repaired, forked, or improved, it works against the purpose of the platform.

Official Mimic recognition requires open-source release under licenses approved by Mimic Labs.

Official Mimic LABS approval

Official approval is optional.

A module can be open-source and community-made without being officially approved. Official approval only means Mimic Labs has reviewed the module and accepted it for official listing, certification, manufacturing, consignment, or sale.

Official approval may review:

  • electrical safety

  • power draw

  • connector behavior

  • firmware behavior

  • mechanical fit

  • user safety

  • documentation quality

  • license compliance

  • manufacturing readiness

  • repairability

  • branding alignment

  • reliability

  • QA requirements

Approval does not mean the original creator gives up authorship. The creator remains credited.

Naming and branding

For officially approved modules, Mimic Labs may request or require a name change if the submitted name does not align with Mimic Labs branding, clarity, safety, product organization, or customer expectations.

This does not mean Mimic Labs owns the creator’s idea. It only means official Mimic listing, certification, packaging, or sale may require a name that fits the Mimic Labs ecosystem.

Creators may still use their own project name outside of official Mimic Labs channels, as long as it does not create confusion or imply official status where none exists.

Certification badge and serial registry

Approved modules may receive an official Mimic Labs certification badge with a unique serial number.

Mimic Labs may maintain a public registry that includes:

  • module name

  • module description

  • creator or author

  • license

  • approval status

  • approval date

  • approval record number

  • version/revision

  • supported hardware

  • source repository link

  • manufacturing status

  • notes or warnings

The registry exists to make the ecosystem easier to trust. Users should be able to tell what is official, what is experimental, what is community-made, and what has been reviewed.

Consignment and manufacturing

Some approved modules may be eligible for consignment, official manufacturing, or sale through Mimic Labs.

This is optional and requires a separate written agreement.

Depending on the module and the amount of work required from Mimic Labs, creators may be eligible to receive a share of profits from official sales.

Mimic Labs may offer up to 50% of net profit to the creator when a module is well-documented, safe, manufacturable, and requires minimal redesign, QA work, support burden, or production changes.

Modules that require significant engineering review, redesign, safety work, manufacturing setup, documentation, packaging, support, or warranty coverage may receive a lower share.

Profit share depends on the actual work required, risk, cost, and support responsibility.

What “profit” means

For consignment or official manufacturing, profit share is based on net profit, not total sale price.

Net profit may account for costs such as:

  • parts

  • PCB fabrication

  • assembly

  • labor

  • testing

  • packaging

  • payment processing

  • platform fees

  • shipping materials

  • failed units

  • warranty reserves

  • customer support

  • certification work

  • documentation work

  • redesign or manufacturing preparation

  • taxes or required business fees where applicable

The exact calculation must be defined in the creator agreement before the module is sold. We want to maintain transparency and ensure a mutually beneficial agreement.

What “profit” means

For consignment or official manufacturing, profit share is based on net profit, not total sale price.

Net profit may account for costs such as:

  • parts

  • PCB fabrication

  • assembly

  • labor

  • testing

  • packaging

  • payment processing

  • platform fees

  • shipping materials

  • failed units

  • warranty reserves

  • customer support

  • certification work

  • documentation work

  • redesign or manufacturing preparation

  • taxes or required business fees where applicable

The exact calculation must be defined in the creator agreement before the module is sold. We want to maintain transparency and ensure a mutually beneficial agreement.

Safety and Quality Assurance

Mimic Labs may reject or delay approval of a module if it creates safety concerns, reliability concerns, unclear documentation, excessive support burden, license conflicts, electrical issues, mechanical issues, or brand confusion.

This is not meant to block creativity. It is meant to protect users and keep the ecosystem trustworthy.

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

Community modules vs. official modules

A community module is a module made by someone in the community.

An official module is a module reviewed and approved by Mimic Labs.

A consignment or manufactured module is an approved module sold through Mimic Labs under a separate agreement.

Not every good module needs to become official. Some things should stay experimental, weird, niche, personal, or chaotic. That is part of the fun.

Official approval only matters when a module wants to use Mimic Labs official channels, badges, certification, manufacturing, or store placement.

Our intent

The goal is to keep the ecosystem open, repairable, understandable, and safe.

We want people to build strange things. We want people to modify our work. We want people to make modules we never would have thought of. We want creators to get credit. We want good community work to have a path toward official recognition and revenue.

Mimic Labs is open where openness helps people build.

Mimic Labs is protected where protection keeps the identity clear.

Functional designs are open and its documentation will be readily available.