Electronics engineering · Palghar, Maharashtra
We design, engineer and manufacture connected electronics.
Indigenous circuit design, multi-layer PCB layout, embedded firmware and device infrastructure — engineered in India for building management, agritech and industrial automation.
Requirement capture to production handover
On-premises or hosted device infrastructure
Design ownership and IP retained by the client
One integrated system
A building is a control problem, not a shopping list.
Most installations are assembled from unrelated products: one vendor for lighting, another for shading, a third for access, a fourth for HVAC. Each arrives with its own controller, its own commissioning tool and its own application. The interfaces between them become the project’s single largest source of cost and delay.
We engineer the control layer as one system. Lighting, shading, climate, access, security, energy and irrigation are specified together, addressed through a common topology and commissioned once — which is why the integration risk disappears rather than being managed.
Fewer interfaces to coordinate. Fewer parties to reconcile on site. A specification the developer, the architect and the electrical contractor can all work from without translation.
Where the cost actually goes
Integration between subsystems, not the subsystems themselves. Every additional controller adds a commissioning window, a support contract and a point of failure nobody owns.
What an integrated topology removes
Duplicate sensing. Conflicting schedules. Four applications for one building. And the argument, eighteen months later, about whose subsystem is at fault.
Systems we engineer
The whole building, addressed as one.
Each of these is normally a separate procurement with a separate controller. Engineered together, they share sensing, scheduling and a single commissioning pass.
Lighting
Circuit and scene control
Switched, dimmed and tunable circuits with presence and daylight input, addressed at the control layer rather than per fitting.
Shading
Blind and louvre automation
Position driven by solar angle, internal temperature and occupancy, coordinated with the climate schedule rather than fighting it.
Climate
HVAC and zone control
Zone-level setpoints, schedules and interlocks, integrated with shading and occupancy so conditioning follows actual use.
Access
Door and gate control
Credentialed entry, time profiles and permission groups, with audit output available to the building operator.
Security
Intrusion and life safety
Presence, perimeter and environmental detection — water, smoke, gas — with alarm routing to the people who act on it.
Energy
Metering and load management
Circuit-level measurement and load scheduling, so consumption is attributable rather than merely visible.
Irrigation
Landscape and estate watering
Zoned scheduling with soil and weather input, for developments, estates and agricultural sites.
Sensing
Environmental instrumentation
Temperature, humidity, air quality, occupancy, level and flow, feeding one telemetry layer rather than four.
Wired, wireless or mixed topology. Control topology is a design decision taken before procurement, not a product preference. A structure under construction is wired because the routes are open. A completed building is wireless because they are not. Most projects are both.
Any structure, any stage, any scale
Where the work lands.
New build
Automation specified at design stage, when control topology, cable routes, panel positions and load planning can still be decided rather than accommodated.
Retrofit
Wireless and hybrid topologies for completed structures. Existing circuits are integrated progressively, without opening finished walls.
Estates and developments
Multi-unit schemes with common-area control, per-unit autonomy and a management view across the whole site.
Plant and agricultural sites
Instrumentation and control for environments defined by dust, thermal load, distance, unstable supply and intermittent connectivity.
Engineering capability
We do not integrate white label boards from China. We design the boards Inhouse.
This is the capability that separates an engineering company from a systems integrator. When a product does not exist, or exists and does not fit, we design it — from requirement to production data.
01
Requirement capture
Function, operating environment, regulatory exposure, target cost and intended volume, specified and agreed before design begins.
02
Schematic design
Circuit designed from first principles, with component selection made against verified Indian distribution availability.
03
Multi-layer PCB layout
Stack-up, power integrity, thermal management and separation of measurement from switching, laid out for the intended fabricator.
04
Embedded firmware
Developed against the mapped hardware, delivered as source the client’s own engineers can read, extend and maintain.
05
Bring-up and validation
First articles assembled, powered and characterised against the specification, with findings fed back into the layout.
06
Enclosure and mechanical
Housing, mounting, ingress protection and installer ergonomics, designed alongside the board rather than after it.
07
Device infrastructure
Provisioning, identity, telemetry, alarms and fleet management — deployable on the client’s own premises.
08
Production handover
DFM review and a complete fabrication and assembly pack, in formats the fabricator and the client both hold.
Engineered and shipped
A decade of our own hardware, on installed walls.
Before we engineered for other companies, we engineered for ourselves — designed, manufactured, distributed and supported under the AutomatiCH® mark, at a quality specification that carried a five-year warranty with doorstep service.
Modular touch switches
Engineered to the 2M Indian modular standard for direct substitution into installed plates and back boxes. No rewiring, no proprietary faceplate, no retraining the electrical contractor.
Glass control panels
A complete size range across 2M, 4M, 6M, 8M and 12M, carrying one control interface from a single bedside point to a whole-floor panel.
Access control hardware
Electronic locking engineered around Indian door construction and frame tolerances, which is a materially different mechanical problem from imported equivalents.
Sensing and detection
Presence, environmental and security instrumentation, wired and wireless, reporting into a single control layer rather than parallel systems.
Multi-protocol by design — Wi-Fi, Bluetooth Low Energy and sub-GHz radio in one device. A control point that stops functioning when the network does is not a control point.
This is a capability record, not a catalogue. The AutomatiCH® retail brand is wound down. There is no consumer channel and no price list on this site. These designs remain in OEM production for the channel partners and contractors who specify them.
Who we serve
Five buyers, and none of them are buying the same thing.
Property developers
Specification
Automation fails commercially when it is specified late. By the time control topology is raised on site, routes are closed, panel positions are fixed and every option remaining is the expensive one.
We specify at design stage: control topology, panel sizing, load planning, cable routing and the commissioning sequence, documented in a single specification your architect, your M&E consultant and your electrical contractor all work from.
Predictable operating cost, and a handover that does not generate a defects list.
Product companies
Design partner
You have a connected product to bring to market and no in-house electronics function. Building one takes twelve months and three disciplines you will need for eight.
We operate as that function for the duration. Requirement capture, schematic, layout, firmware, device infrastructure and a DFM-ready production pack, each stage authorised before the next begins.
Your brand on the product. Design ownership and intellectual property retained entirely by you.
Channel partners and contractors
Continuity
You specify under your own name. When a manufacturer withdraws a line or a component reaches end of life, the commercial exposure is yours, not theirs.
The designs you already install remain in OEM production, and we continue to issue variants, revisions and end-of-life redesigns on request. The quality specification has not been reduced and will not be.
No orphaned installations, and a manufacturer who answers the phone.
Industrial and agricultural operators
Hard environments
Plant and land impose conditions a commercial building never does: particulate ingress, sustained thermal load, long cable runs, unstable supply and connectivity that fails precisely when a reading matters.
We engineer instrumentation, control and telemetry against those conditions specifically, and deploy the data layer on infrastructure you own rather than a subscription you cannot exit.
Measured, controlled and reported — and portable if you move.
Architects and M&E consultants
Design freedom
Automation earns its place when it serves the design intent rather than constraining it. Too frequently it arrives as an incompatible equipment schedule the drawings then have to absorb.
Engineered as one system, lighting, shading, climate and access are coordinated at specification stage, so the technology resolves into the building instead of appearing on it.
Planning certainty, one point of technical responsibility, and no surprises at commissioning.
Project delivery
Four stages, each authorised before the next.
Hardware cost is committed early and discovered late. Staging the engagement means the expensive decisions are taken with information rather than optimism.
STAGE 01
Specify
Function, operating environment, regulatory exposure, target cost and volume. The lowest-cost stage by design, because it is where a project is correctly stopped.
STAGE 02
Engineer
Schematic, multi-layer layout and firmware, with component selection against verified supply. Delivered as functioning first articles, not visualisation.
STAGE 03
Connect
Provisioning, identity, telemetry and alarms. Deployment model — client premises or hosted — is fixed here, because firmware is built to it.
STAGE 04
Transfer
DFM review, full production pack, firmware source and commissioning documentation. The design transfers to the client in full.
Data residency
Device infrastructure, deployed on your premises.
Connected products conventionally report to the manufacturer’s infrastructure. Operationally that places a client’s facility, plant and occupancy data outside their control — subject to a third party’s commercial terms, pricing and continued existence.
We engineered the alternative and shipped it. Provisioning, telemetry, control and alarms can be deployed entirely within the client’s own estate: their hardware, their network, their data, with no external hosting dependency.
That was an unconventional position when we built it. For institutional, industrial and defence-adjacent procurement it is now frequently a condition of award rather than a preference.
Client-premises deployment
Client-premises deployment
The full device infrastructure inside your estate. Nothing egresses unless you specify that it should.
Hosted deployment
The same infrastructure operated by us, where running it in-house is not warranted. A decision taken on merit, not a default.
Migration between the two
A supported transition, specified at design stage. Not a renegotiation later.
Channel and references
Specified and installed by businesses that carry their own reputation.
Engineering a reliable system is one half of the work. Being specified by contractors and developers who are personally accountable for the installation is the other, and it is the half most Indian hardware companies never reach.
Channel and franchise
Sprytny Domotics Private Limited
Ranchi and Dhanbad, Jharkhand
Disney Home Developers
Patna, Bihar
Sai Shakti Engineering Works
Andheri, Mumbai
Next Innovation
Mumbai
Specifying clients
Parmeshwar Yadav
Construction contractor, Mumbai
Vishal Constructions
Construction company, Mumbai
Construction businesses do not trial unproven systems on a live programme. They specify what has already performed, and they are slow to change it — which is precisely why the specification is worth earning.
RitzSCHA™ platform
A decade of hardware engineering, built into a platform.
Every product we have engineered required the same sequence in the same order: research, specification, schematic, layout, firmware, production data and an operational layer once the device is in the field. Executing that repeatedly — for our own products and for our clients’ — established precisely where it fails and how much of it is identical every time.
RitzSCHA™ takes an idea for an electronic product through to a manufactured, connected product — and then operates it in the field.
The platform is operated by WeBiii Traume Private Limited, our subsidiary. Chandrahas Technologies designed it, and continues to engineer the hardware, the systems and the buildings it serves.
Frequently asked
The questions that come before a brief.
What does Chandrahas Technologies actually do?
We design, engineer and manufacture connected electronics. That covers requirement capture, schematic design, multi-layer PCB layout, embedded firmware, device infrastructure and a production handover a fabricator can build from. We apply it to building management, agritech and industrial automation, either as a complete system for a site or as an engineering partner to a product company.
Can I buy switches or control panels directly from you?
No. The AutomatiCH® retail brand is wound down and there is no consumer channel, so there is no shop or price list on this site. Those designs remain in OEM production for the channel partners and contractors who already specify them. For a project, the route in is an engineering consultation rather than a purchase.
Do you engineer hardware for other companies under their own brand?
Yes, and that is now the majority of our engineering work. We take a product from requirement capture through schematic design, layout and firmware to a DFM-ready production pack. The client’s brand goes on the product and the intellectual property in the design is retained by the client. We have held that position in both directions for a decade.
Can device infrastructure run on our own servers instead of yours?
Yes, and it has shipped that way. Provisioning, telemetry, control and alarms can be deployed on infrastructure the client owns, inside a facility the client controls, with no external hosting dependency. This is specified at design stage rather than retrofitted, because device identity and firmware are built differently for each deployment model.
Do you certify the products you design?
No. Safety, electromagnetic compatibility, radio and environmental approval for the client’s target markets remains the client’s responsibility unless separately agreed in writing. What we do is design against those requirements from the outset and identify which standards apply, so certification becomes a test to pass rather than a redesign to fund.
How is a building automation project specified?
We establish control topology first, which means deciding wired, wireless or mixed before anything is procured. From there we size panels, plan loads, position control points and document the system so the developer, the architect and the electrical contractor all work from one specification. Commissioning and handover documentation are part of the same scope.
What happens to installed AutomatiCH® systems now the retail brand has wound down?
They remain supported and buildable. The designs stay in OEM production for the contractors who carry them, and we continue to issue variants and revisions on request, including redesign around end-of-life components. Design continuity was a deliberate commitment, not a transitional arrangement.
What is RitzSCHA™ and how does it relate to Chandrahas Technologies?
RitzSCHA™ is the platform that takes an idea for an electronic product through to a manufactured, connected product, and then operates it in the field. It was designed by Chandrahas Technologies out of a decade of hardware engineering, and it is operated by our subsidiary WeBiii Traume Private Limited.
What work will you not take on?
We do not design weapons, which includes seekers, fuzing and military datalinks. We do not undertake flight-critical avionics or medical devices, both being regulated categories with qualification burdens we do not discharge. We do not sell or pool customer data, and no mechanism to do so exists in anything we build.
Who owns the design at the end of an engagement?
The client does. Schematics, layout data, firmware source and the production pack are handed over in formats a fabricator and the client’s own engineers can open and maintain independently. The design can be taken to any manufacturer, and stating that at the outset is usually why clients stay.
Engineering consultation
Bring us the specification, the site, or the problem.
Describe the function, the operating environment and the constraints. We will set out what it takes to engineer, what governs the cost, and whether it should be built as specified. No charge and no obligation.
RitzSCHA™ is the generative AI platform for Indian hardware innovation. From idea to market in weeks, not years. Multi‑tenant safe, sovereign cloud, and built for MSMEs.