Dreamfyre is a parent company. Products are built and run underneath it, each with its own name and its own team. The first is in build now, and it appears here with a date and a link the week it goes live.
Dreamfyre holds the products. Each one gets its own name, its own team and its own reason to exist. Dreamfyre is the thing underneath them, not the label on the front.
It ships when it is genuinely ready, and it appears here the week it goes live. No countdown, no waitlist, no teaser.
Small on purpose. The team grows when a second pair of hands changes the product, not the headcount.
Every product stands on its own. They share the parts worth sharing: infrastructure, a design language, and whatever the last build taught us. That sharing is the reason to hold them under one company instead of scattering them.
Dreamfyre was founded in 2026 in Delhi to build and hold a small number of products. Not client work and not consulting: products with their own names, built to outlast the attention that launches them.
Today that is one founder, one product in build, and a fairly clear idea of what the second could be. Writing that down publicly is the point. It is easier to hold yourself to a plan people can read.
Or you want to build one. Either way it reaches me directly, and I answer.
hello@dreamfyre.in →Working here. No roles are open yet, because there is no product to staff. If you build things and want to be early somewhere, write anyway. Those notes get kept and read again when hiring starts.
Partners and collaborators. Same address. Tell me what you are building and where you think it overlaps.
