Tubular Daily Care started as the visible brand because the product needed its own voice, its own domain, and its own momentum.
Now the company needs a stronger parent layer above that product story.
This migration is not about burying Tubular. It is about giving it a clearer place inside a broader company narrative.
For families, providers, and future partners, that shift matters. A stronger parent company layer creates more context around the product without taking away the product-specific language that made Tubular useful in the first place.
Why move now
Moving Tubular into products/tubular gives MediTracer a durable information architecture early:
- the parent company gets its own homepage and legal foundation
- the product keeps its own route space and blog
- future products can follow the same model without another rewrite
Making that change early is less disruptive than waiting until more products, more pages, and more redirects are already in motion.
It also gives the team a cleaner way to explain what MediTracer is: not just one product website, but a company building a family of healthcare tools around daily home-care routines.
What stays product-specific
Tubular still owns its product narrative, download path, and blog.
That means the public experience can still feel like a focused product brand while the shared codebase starts doing company-level work in the background.
Families looking for Tubular information should still feel like they arrived in a product-specific space. They should not have to sort through unrelated company messaging just to understand what the product is for.
That separation also makes it easier to keep product updates specific. Product publishing can stay close to the reality of enteral feeding management while the parent company develops its own broader voice more deliberately.
What this unlocks
The biggest long-term benefit is a cleaner redirect plan.
When the team is ready, tubular.health can point into the equivalent MediTracer paths instead of existing as a permanently separate web property.
It also unlocks a clearer internal structure for everything around the product: navigation, trust pages, future product areas, and any company-level storytelling that needs to sit above individual product routes.
That is the real goal of the move. Tubular remains recognizable, but it now sits inside an information architecture built to support what comes next.