Zum Inhalt springen

rbAmp for Labs, R&D, and Startups

Build your product on the same hardware we use internally. Volume pricing from 10 units, lab collaboration with NDA, OEM and white-label options from 500+ annual. We are looking for end-user partnerships — labs running power-quality studies, startups designing energy products, and OEM integrators building rbAmp into a larger system. For wholesale distribution / reselling, see Become a Distributor instead.

Who B2B is for

The B2B program serves three concrete profiles:

Research labs and universities

You run power-quality studies, calibration testing, or build instrumented testbeds. You publish papers and you need:

  • Lab-grade accuracy without lab-grade prices (PRO tier ships sub-$50)
  • Raw register access so you can capture data the way your protocol needs it
  • Calibration certificates for traceability in publications
  • Custom firmware tweaks for unusual measurement scenarios

We hold sample PRO units for academic groups during the early-access window. Email [email protected] with your institution, group, and a short description of what you would measure.

Energy startups

You are building a product on top of AC metering — submetering services, building energy management, EV charging telemetry, IoT energy gateways. You need:

  • Hardware that doesn't constrain your software design
  • A protocol you can read in two days (the API Reference is the contract, not a summary)
  • A library that's easy to fork and customise
  • A volume pricing path so unit economics work as you scale

We do NDA collaboration through R&D phase, then formalize volume contracts when you ship.

OEM integrators

You sell a larger system — solar inverters with integrated metering, sub-metering panels, industrial control cabinets — and you want rbAmp inside it. We support:

  • Volume pricing from 100 units
  • White-label option at 500+ units annual: your brand on the silkscreen and packaging
  • Custom firmware compilation (within reasonable engineering effort)
  • Direct production scheduling so your supply chain plans around real dates

What we deliberately do NOT do

Honest about scope so you do not waste your time:

  • Mass installer channel — residential / commercial sub-metering as a turn-key service. We ship hardware. Installer programs are run by sub-metering OEMs; we are happy to be the hardware behind their service, but we do not operate that channel ourselves.
  • MID-certified billing meters — no MID certification on the roadmap. For tenant invoicing where regulation requires certified meters, look at Iskraemeco, Itron, or similar. We can be the second meter in the chain for analytics.
  • Plug-and-play retail through big-box channels — that audience is served by the Wireless line via Amazon / AliExpress consumer channels. B2B is for technical end users.

If you are looking for one of the above and the gap is genuinely on us, talk to RocketController parent — sister brands may fit.

Volume pricing

Volume per order Discount Lead time Payment terms
10–49 units 10 % off retail 1–2 weeks Prepayment
50–99 units 20 % off retail 2–3 weeks Prepayment (first 2 orders), then Net-30
100–499 units 25 % off retail 3–4 weeks Net-30
500+ units Custom quote, possible OEM / private label 6–8 weeks Negotiable, typically Net-45

Lead times are bench-realistic, not optimistic. We confirm dates after stock check.

Lab and startup support

For Tier 2 / Tier 3 B2B partners (50+ units), we provide:

  • Pre-sale technical consultation. 30-minute video call with an engineer to walk through your integration before you commit to volume.
  • Custom firmware compilation. Examples we have shipped: alternative I²C addresses outside the default range, larger period accumulator buffer for non-standard sampling, vendor-specific status registers. Reasonable engineering effort; documented quote.
  • Integration support during pilot. Slack / Discord channel with our firmware engineers for the first 30 days of your pilot deployment.
  • Bulk shipping coordination. DDP options for EU / US so customs clearance is our problem, not yours.

Apply for B2B pricing

B2B inquiry form coming online with the next deploy. Until then, email [email protected] with:

  • Company name + country
  • Use case — short description of what you are building / measuring
  • Volume estimate — honest first-year projection, not aspirational
  • Timeline — when do you need first units, when does production ramp
  • Tier interest — Volume only, or Volume + custom firmware, or Volume + private label
  • Technical contact — name + email of whoever will integrate the modules

We respond within 1–2 business days. For projects beyond 100 units we book a 30-minute video call to walk through pricing, payment, and roadmap fit.

Documentation for evaluation

Before you commit:

Case studies (coming)

We will publish case studies as Tier 2 / Tier 3 partners give us permission. Until then, talk to us directly — we can introduce you to a current partner under NDA if their use case maps to yours.

Frequently asked

Can I buy 5 units at retail and skip the B2B form? Yes — under 10 units, just use the regular shop at retail pricing. The B2B form only matters at volume.

Do you ship internationally? EU, UK, US, Canada, Australia, New Zealand, Japan, South Korea, most Southeast Asia. Other countries — case-by-case (email us with the country and we will check customs / VAT). EU stock from France; China stock from Zhuhai.

Can I get a sample unit before committing to volume? Yes for Tier 2+ B2B (50+ unit projection). One free sample of any single SKU; for additional samples we charge production cost. Email [email protected] with the project context.

Is the firmware locked, or can I modify it? rbAmp firmware is closed (binary). The Arduino / ESP-IDF / MicroPython libraries that talk to the firmware are open source — those you can fork freely. For custom firmware behaviour (different registers, custom protocols), that goes through the B2B custom firmware program.

Do you offer NDA collaboration before formal pricing? Yes for Tier 2 / Tier 3. We can sign a mutual NDA before the first technical call so you can share design context without exposure.

Related