Simple by default.
Make setup, calibration, and integration understandable. Explain the complete system a developer needs, including its cost and limitations.
Brand guidelines
Accurate tracking.
A clear identity.
opentags should feel precise, direct, and easy to work with. Our identity makes room for a family of tracking products.
Mission
Make accurate tracking accessible to people building robots.
Accurate tracking. Built for robotics.
We build tracking hardware and integration tools to help robot developers measure position and motion.
Principles
Useful. Understandable. Measured.
Clear about capabilities.
Support accuracy claims with measurements and stated test conditions. Distinguish measured results, development targets, and planned capabilities. Name the resources actually available.
Products
One company. A family of products.
opentag U1
UWB ranging and localization
Measure distance and develop indoor positioning with UWB hardware, calibration tools, and robot integration guides.
Explore U1 →opentag U2
UWB with inertial measurements
Planned with an onboard IMU and the OWM3000 module, our custom counterpart to DWM3000, with separate clock and sync ports.
Coming Soon
opentag S1
Shared synchronization hardware
Sync 1 is intended to distribute clock and synchronization signals to U2 setups.
Coming Soon
Guidelines
Naming
- Write the company as opentags: lowercase, plural, one word. Use open-tags only in existing URLs and account names.
- Use singular opentag for product names, with uppercase family letters and generation numbers: opentag U1, U2, S1. Pair short names with a useful descriptor.
- Name packages U1 Distance Kit and U1 Location Kit. Keep PCB revision numbers separate from product generations.
- Preserve historical identifiers, firmware commands, asset filenames, and published data. Redirect retired page URLs and retain section links.
Guidelines
Voice and evidence
- Lead with tracking for robotics. Explain UWB within the relevant product, rather than defining the whole company by a radio technology.
- Use concrete language and useful details. Avoid unsupported superlatives and vague claims of precision.
- Describe measured performance with its setup, conditions, and limitations on the relevant product and performance pages. Label goals as targets and future features as planned.
- Place Coming Soon at the bottom of each upcoming product card, aligned with available-product links, and style it bold and italic. Use bold text for product-card links. Omit status labels for available products. Keep product cards concise: name, descriptor, description, and Coming Soon where applicable, without extra caveats beneath the card or product grid. Do not offer a purchase action for an unreleased product.
- Describe public resources individually. Do not promise that all hardware or firmware is open source. Hardware design files are not currently published; this is not a declaration of future licensing policy.
Guidelines
Typography
- Use Editorial New for major marketing headlines and short titles over product photography.
- Use system sans for navigation, body text, section headings, labels, controls, and specifications.
- Monospace is allowed for code, logs, commands, and identifiers when it improves readability.
Built for robotics.
From setup to useful measurements.
Code example: ros2 topic echo /opentags/range
Guidelines
Color and interface
- Use the shared monochrome palette for branding. Reuse the shared CSS tokens for fonts, color, spacing, content width, and four-pixel control corners.
- Use thin borders and generous spacing. Let the hardware and measured evidence carry the page.
- Functional colors are allowed for warnings, errors, success, and measurement series. Pair color with labels, shapes, or other cues; never communicate status through color alone.
- Dark instrument panels, circular data markers, and technical diagrams are functional exceptions. Review keyboard focus, contrast, and mobile layout.
Guidelines
Imagery
- Show real hardware, connections, and use contexts. Clearly label illustrations and simulated data.
- Keep image titles short and readable. Use a subtle neutral gradient where a title overlays photography.
- Identify the pictured product correctly. Do not present U1 photographs as images of U2 or S1.
