Our datacentres

What ARAN is for

TN-DC01 is where NexusSec runs its own infrastructure and compute rather than renting someone else's. Two things follow from that, and both matter more to a client than a specification sheet does.

The first is data residency. Anything we host for you at this facility stays in India. If that is relevant to your obligations, including under the DPDP Act, it can be written into the engagement rather than assumed. Our DPDP readiness page covers where that fits and, equally, where it does not.

The second is control. When we operate the facility, the people who designed your network are the people with access to the hardware it runs on. There is no third party in between to escalate through when something needs doing at three in the morning.

Where it is, and why we are vague about it

TN-DC01 is in the Tenkasi region of Tamil Nadu. That is as precise as this page gets, and the imprecision is the point. Publishing a datacentre's street address tells anyone who wants to know exactly where to find the hardware, and no operator with sensible practices does it. If you are evaluating us seriously and need specifics, we will provide them under NDA.

Two locations, two different jobs

It is worth being precise about this, because "we have a datacentre" is a claim that often gets stretched. NexusSec has one office and one facility, and they do different things.

The office in Airoli, Navi Mumbai is where the engineers are. That is where engagements are scoped and run from, and it is the radius we attend site in: Navi Mumbai, Mumbai and Thane, with remote delivery across India. Nothing on this page changes that.

TN-DC01 in Tamil Nadu is infrastructure, not a second office. There is no sales presence there and we do not claim local coverage in Tamil Nadu on the strength of it. If you are in Chennai or Coimbatore and want somebody on site, we are still a remote-delivery option for you and we will say so plainly.

Reading the designation

The naming is deliberate rather than decorative. TN is the state, DC the facility type, 01 the sequence. A second facility in the same state would be TN-DC02; one elsewhere would carry its own state code. Codenames like ARAN are how we refer to a site internally, in change tickets and runbooks, where a designation string is easy to mistype and easy to confuse.

This matters to you only in one respect: when we reference a facility in a report or a change record, the reference is unambiguous.

What this changes for a client

For most of our engagements, nothing. A firewall replacement in Turbhe or a VAPT for a manufacturer in Taloja does not touch this facility at all, and we would not pretend otherwise to make the page sound more relevant than it is.

It becomes relevant in three situations. When a client needs infrastructure hosted and wants it hosted in India rather than in an overseas region. When data residency is a stated requirement rather than a preference. And when a client wants the people who designed their network to be the same people with physical access to the hardware it runs on, instead of a chain of subcontractors.

What we are not claiming

Facility pages in this industry tend to arrive decorated with tier ratings, uptime percentages and certification logos. We have published none of those here, because publishing a number we cannot evidence is worse than publishing nothing.

So, plainly: this page does not claim an Uptime Institute tier, a specific availability figure, a power or cooling capacity, a carrier list, or any third-party certification. If you need those for a procurement process, ask on a call and you will get either the real figures or an honest "not yet".