DEV Community: Yash Kumar Gupta

We Didn’t Start With Anethix Labs

Yash Kumar Gupta — Tue, 15 Sep 2026 12:27:23 +0000

I wasn’t planning to write about Anethix Labs again.

But after reading what has recently been written about the company and about the people who were part of it, I felt that there was one part of the story missing.

When I look back at how Anethix Labs started, one thing still feels funny to me:

Anethix Labs was never the original idea.

There was no plan saying, “Let’s start a software company called Anethix Labs.”

We didn’t even start with Anethings.

We started with two completely different projects, a lot of uncertainty, and four people trying to figure out what we could actually build.

One of those projects was Ane Rentals, a car-rental application.

The other was Troql, a project I was working on personally.

And, in a way, Troql played a much bigger role in the story of Anethix Labs than I understood at the time.

Before there was a company

I was already working on Troql before Anethix Labs existed.

The idea was to make it easier for developers to understand unfamiliar codebases and get onboarded into projects faster.

I built an early version, launched it, and posted about it on X.

I wasn’t expecting anything extraordinary.

But within around 48 hours, three people had actually used it one from Japan, one from San Francisco and one from Bangalore.

Three users.

That’s it.

Today, three users sounds almost insignificant.

Back then, it meant a lot to me.

It was the first time I had built something and had people I didn’t know, from different parts of the world, actually try it.

At the same time, the four of us were working on Ane Rentals.

Eventually, we started thinking about turning our projects into something more serious.

For that, we needed a legal entity.
So we went to Assam Startup.

And that’s where the direction of everything started changing.

“The car rental business isn’t that simple.”

We showed them Ane Rentals first.

The response was something we hadn’t really anticipated.

Building the application was one thing.

Actually operating a car-rental business in India was another.

There were regulatory requirements and legal complications that made the business much more difficult than we had assumed.

So we started talking about Troql.

I explained what it was, what problem it was trying to solve, and mentioned the early users.

The person we were speaking with was interested in the idea and told us to work on it more seriously and see whether we could develop it into a deep-tech project.

That was the first time I started thinking:

Maybe Troql could actually become something bigger.

We also asked about getting support to establish a company.

Instead of simply telling us to go register one ourselves, we were directed towards our university’s Venture Labs.

And that eventually led to the four of us sitting in front of the Venture Labs team.

The question that made us think

We presented Ane Rentals again.

Same problem.

The regulatory side made it difficult.

Then we showed Troql.

The questions came quickly.

Who is the customer?

Who would actually pay for this?

Why would an MNC use it if they could build something internally?

We didn’t have polished startup answers.

We were students.

We were still figuring things out.

But we could at least say one thing:

People were already using it.

I told them about the three users from Japan, San Francisco and Bangalore.

The team understood the concept, but they also made it clear that we needed to figure out the business model and target users much better.

We were given forms to fill out with the project details.

For the first time, the idea of actually forming a company started becoming real.

Then we had to choose

There was just one problem.

The Venture Labs could support the registration of only one company.

So the four of us had to decide.

Troql or Ane Rentals?

We discussed it.

Troql had potential, but taking it towards an enterprise product would require resources we simply didn’t have.

Ane Rentals looked like the easier route to generating revenue.

So we chose Ane Rentals.

And then, ironically, the same problem that had come up in the meetings became impossible to ignore.

The more we researched the regulations, the more we realised that we couldn’t realistically run the business the way we had imagined.

So the project we had spent so much time building had to change.

The pivot that eventually became Anethings

We didn’t want to throw away everything we had built.

So we started thinking:

What if the rental concept wasn’t limited to cars?

And that’s how Ane Rentals slowly became Anethings.

The idea changed from renting cars to allowing people to rent different kinds of things.

We started modifying the product.
Then we tried to move ahead with the company registration.

The name we wanted wasn’t available.

So once again, we had to stop and rethink.

This time, we weren’t just thinking about the app.

We were thinking about the company itself.

What if we created a software company that could build software for clients while also developing our own products?

That idea made more sense.

And eventually, we settled on the name:
Anethix Labs.

Anethings would be one product.

Troql would be another product we wanted to develop.

And Anethix Labs would be the company behind them.

That’s how it happened.

Not through one big decision.

Through a series of decisions that kept changing the direction.

What I understand differently now

At the time, I thought the difficult part was building the technology.

Now I think that was only one part of it.

Building something with other people is a completely different experience.

You can have the same idea, sit in the same meetings, work on the same product and still walk away with completely different memories of what happened.

That’s probably normal.

Everyone remembers the part they were closest to.

For me, the technical side was always the part I was closest to.

I was working on Troql before the company existed, and when we started working towards Anethix Labs, I was also involved in the technical development of the products.

So when I look back at those early days, I don’t just remember the company registration.

I remember the projects before the company.

The first version of Troql.

The first three users.

The Assam Startup meeting.

The Venture Labs meeting.

The questions we couldn’t answer properly.

The decision to choose Ane Rentals.

The night we changed the idea.

The birth of Anethings.

And eventually, the name Anethix Labs.

That’s what the beginning looked like from where I stood.

I don’t think a title tells the whole story

One thing this experience taught me is that titles are easy to remember, but contributions are harder to measure.

Someone can be a CEO.

Someone can be a CTO.

Someone can be a managing director.

Someone can be a developer.

Someone can be the person handling finance.

But a title doesn’t tell you what happened before the title existed.

And a title doesn’t automatically make someone a leader either.

I learned that leadership is much more visible in how someone behaves when things don’t go according to plan how they communicate, handle disagreements and take responsibility.

That’s something I will carry with me long after Anethix Labs.

I eventually walked away

My time with Anethix Labs eventually came to an end.

I made that decision knowing that the company would continue without me.

And it did.

People continued working.

The company changed.

The team changed.

The products changed.

That’s how startups work.

When you leave something, you don’t get to own everything that happens afterwards.

And I don’t want to.

The work done after my involvement is not mine to claim.

But I also don’t think leaving means that everything you did before leaving disappears.

I can acknowledge what others built after I left while still acknowledging what I contributed when I was there.

Both can be true.

Maybe that’s what Anethix Labs really taught me

When we started, I thought we were trying to build an app.

Then the app changed.

The business model changed.

The company name changed.

The product changed.

Our plans changed.

Eventually, even the people changed.

And somewhere along the way, I realised that startups aren’t really about following the original plan.

They’re about making decisions when the original plan stops making sense.

Sometimes you pivot.

Sometimes you start again.

Sometimes you keep going.

And sometimes you walk away.

I don’t know what Anethix Labs will eventually become.

But I know what it meant to me.

It was the first time I got to experience what it feels like to take something that exists mostly as an idea and try to turn it into something real.

And for me, that story didn’t begin when Anethix Labs Private Limited was incorporated.

It began much earlier.

With a project called Troql, three unexpected users, a car-rental app that didn’t work out, a lot of questions, and four students who didn’t really know where all of this was going.

Looking back, maybe that’s what made it worth experiencing.

Yash Kumar Gupta Co-Founder, Anethix Labs

Building Anethix Labs From the Ground Up: What I Learned as a Co-Founder

Yash Kumar Gupta — Tue, 15 Sep 2026 11:58:16 +0000

I was one of the Co-Founders of Anethix Labs Private Limited, and my involvement with the company started before Anethix Labs was even legally incorporated.

In the beginning, there was no established company, no finished product, and no large team. There was simply an idea and a small group of people trying to turn that idea into something real.

From the early stages, I was responsible for handling the technical side of Anethix Labs. I worked on the product, development, technical architecture and the different decisions involved in turning an idea into a working software product.

That period gave me my first real experience of what it means to build something from the ground up.

Building Before the Company Was Official

One of the most interesting parts of my experience with Anethix Labs was that the work started before the company itself was formally incorporated.

We were already discussing the product, working on the technical side and trying to figure out how everything would come together.

Later, Anethix Labs Private Limited was formally incorporated, but by then I had already spent considerable time working on the technical foundation of what we were trying to build.

Being involved from that early stage taught me that building a company is very different from simply having an idea for one.

An idea is easy to discuss.

Turning it into something usable requires time, experimentation, technical work and a lot of decisions that aren’t obvious at the beginning.

My Role at Anethix Labs

As a Co-Founder, my primary contribution was on the technology and product-development side.

I was involved in developing the product and dealing with the technical problems that came with building it from scratch. There were many things that had to be figured out along the way what to build, how to build it, what technologies to use and how different parts of the product should work together.

It wasn’t a large engineering organisation with clearly separated teams and responsibilities.

It was a small startup environment where you often had to figure things out yourself.

That was probably one of the most valuable parts of the experience.

I wasn’t simply working on an assigned task. I had to think about the product as a whole and understand how technical decisions affected what we were trying to build as a company.

What I Learned About Startups

My biggest takeaway from Anethix Labs wasn’t a particular programming language or technology.

It was understanding how much people and communication matter when building something together.

Technology can solve many problems, but it cannot solve a lack of communication or trust between people.

There were good periods, difficult periods, disagreements and mistakes. Looking back, I think all of them were useful in their own way because they showed me what working in a startup environment actually looks like.

One lesson that stayed with me is simple:
“A title doesn’t make someone a leader.”

Leadership becomes visible when things become difficult, when people disagree, and when decisions don’t go as planned. It is reflected in how people communicate, how they treat one another and whether they take responsibility.

It Wasn’t a Huge Startup Story

I don’t want to present Anethix Labs as some massive startup success story. It wasn’t.

It was a small company and an early-stage attempt to build a product. But I don’t think an experience has to become a huge success to be valuable.

For me, the value was in getting to experience the entire process from the beginning just starting with an idea, working on the technology, building a product, working with other people and learning from the things that didn’t go as expected.

Those are experiences that are difficult to learn from a classroom alone.

Moving Forward

My time actively working on Anethix Labs eventually came to an end, but the experience has stayed with me.

It changed how I look at software development, startups, teamwork and leadership.

More importantly, it gave me a much clearer understanding of the kind of environment I want to work in and the kind of person I want to become when building something with others.

I’m grateful that I got the opportunity to experience Anethix Labs from its earliest days.

It wasn’t perfect, and there are things I would do differently today.

But that’s probably the point.

You don’t need every experience to become a success story.

Sometimes, building something from scratch, seeing what works, seeing what doesn’t, and learning from the people around you is valuable enough.

— Yash Kumar Gupta
Co-Founder, Anethix Labs

Stop getting lost in the Next.js App Router: I built an open-source visualizer

Yash Kumar Gupta — Tue, 16 Dec 2025 10:39:35 +0000

I love the Next.js App Router, but let's be honest: once your project grows beyond 10 pages, the file structure gets messy.

You end up with deeply nested folders, page.tsx files everywhere, and it becomes impossible to visualize the actual user flow just by looking at the file explorer.

The Problem: VS Code shows you a list of files. It doesn't show you the architecture.

The Solution: Troql I spent the weekend building a tool to fix this. Troql parses your GitHub repository and generates an interactive node-map of your entire application structure.

Key Features:

🗺️ Visualizes Layouts vs Pages: See exactly which layouts wrap which routes.

⚡ Direct VS Code Integration: Click any node in the map to instantly open that specific file directly in your VS Code editor.

🔒 100% Client-side: It uses Babel AST to parse the code securely in your browser.

How it's built (The Tech Stack):

Framework: Next.js (obviously)

Parsing: Babel AST (to read the file structure)

Visualization: React Flow (for the node graph)

It’s fully open-source. I’m looking for feedback on the visualization logic—does it handle your (groups) and [dynamic] routes correctly?

🔗 Try it live: https://www.troql.com/demo
💻 Source Code: https://github.com/yashkr321/troql

Let me know what you think in the comments! 👇

⚠️ Note on Performance (Groq API)

To keep this project open and free, the live demo is currently running on the Groq Free API.

The Good: It's blazing fast ⚡

The Bad: You might hit a rate limit if too many people use it at once.

If it stalls, please give it a minute and try again! I plan to upgrade to the Pro tier soon for better stability.