Home Automation
Control software that coordinates home equipment, from lighting and climate to everyday scenes.
Software Development
Dade Fanavaran Pooya is a small software team in Shahrood. We work on home automation, data collection, the Internet of Things, mobile programming, and web development — from control logic inside a house to the interface a resident, operator, or customer uses every day.

Home automation means software that understands the real state of a house, not only a row of smart switches.
The company is organized around these subjects. Each area has its own page so it is clear what kind of project fits this team — from home control and IoT to data collection, mobile, and web.
Control software that coordinates home equipment, from lighting and climate to everyday scenes.
Collecting and structuring data that arrives from sensors, forms, or existing systems.
Connecting devices to software, and moving status and data between node, gateway, and service.
Mobile applications for monitoring, control, and working with data, together with the service behind them.
Sites and web applications for presenting the work, managing information, and staying in touch.
A project usually starts when a device, a data path, or an interface needs defined behavior and there is not enough internal capacity to build that software layer.
When lighting, climate, or everyday scenes must stay coordinated, and a dropped link must not leave the system ambiguous.
When sensors, forms, or an existing system must become a traceable flow — what was recorded, when, and from where.
When a customer or operator must reach status and commands from a browser or phone, clearly and in step with the service behind it.


A few examples of software we have built and that you can open directly — not a public client list.
01
A web system for browsing and comparing bank loans and credit products.
How the work is approached
Three commitments we start projects with. This site does not publish performance figures or a public client list — only the commitments that matter when software is handed over.
01
Before tools are chosen, the scope is made plain: which devices or data are involved, who will use the result, and what sits outside this phase.
02
The result has to be something that can be installed, explained, and handed over. A technology name is not the value. Specific, testable behavior is.
03
Homes, local networks, and mobile links are not lab conditions. The design is set for that reality, rather than a permanent and perfect connection.
A short description of the work is enough: which devices or data are involved and what result you need. Leave a phone number or email so a reply is possible. The message is stored on this site.