About AKAYA

AKAYA started on October 21, 2025, as a personal experiment by Jeet Sah, a 13-year-old developer from India.

There was no company, no team, and no plan to turn it into a product.

The first version was little more than a chatbox and a message system connected to Llama 8B Instant through Groq. It was simple enough that, looking back, it felt more like a school project than the beginning of something Jeet would spend almost a year building.

Then came a tiny moment that changed how he looked at it.

After getting the first version working, Jeet typed:

“are you akaya”

And it replied:

“Yes. I am AKAYA...”

Technically, nothing extraordinary had happened. An AI model had responded through an interface.

But for a few seconds, Jeet stopped thinking about APIs, code and bugs. He stopped looking at AKAYA as something he was programming and started looking at it as someone actually using it.

For the first time, AKAYA felt real.

And the experiment kept growing.

AKAYA was never about trying to build a smarter foundation model.

The models Jeet was already using were incredibly capable. What bothered him was everything around the models.

AI could feel slow. Privacy could feel like an afterthought instead of something the product was designed around. Useful capabilities were scattered across different tools and services. And products described as accessible could suddenly become much less useful once you ran into restrictive usage limits.

Jeet wanted to see what the experience could look like if those things were treated as fundamental parts of the product.

So he kept building.

The original chatbox gradually became something much larger.

Personal Memory gave conversations continuity. Projects created dedicated spaces for longer-running work. Group Chats explored conversations involving multiple people and AI. Scheduled Tasks allowed useful AI work to extend beyond a single conversation. Full-duplex Voice began pushing AKAYA beyond typing.

And the idea expanded further: images, video, audio, 3D and other capabilities working together instead of feeling like a collection of disconnected tools.

What started as an experiment was becoming a connected AI workspace.

AKAYA has been independently designed and built by Jeet.

There isn't a large engineering or design team behind it.

Jeet decides how the product should work: its interface, features, behavior, systems and overall direction. AI-assisted coding is used extensively throughout development to help turn those ideas and decisions into working software.

And over time, one lesson became especially clear:

Adding features isn't the hardest part. Making them dependable is.

Getting something to work once during development is very different from building something real people can open every day and trust to keep working.

Features that looked finished revealed problems when they were actually used. Systems were redesigned. Experiments were abandoned. Parts of AKAYA were rebuilt when better approaches became possible.

Some problems took days.

Others took much longer than expected.

But each iteration moved AKAYA further away from that first little chatbox.

As AKAYA grew, so did the amount of time and effort required to keep building it.

There were moments when Jeet seriously considered stopping.

But one thought kept coming back:

After putting so much into AKAYA, stopping before anyone had even seen what it became would mean the entire project could simply disappear without ever getting its chance.

So he kept building.

Now, almost a year after that first experiment, AKAYA bears little resemblance to where it started.

But the principles behind it haven't changed very much.

AKAYA isn't being built to become another chatbot with a longer feature list.

The longer-term idea is much bigger:

One connected place for AI.

A place where conversations don't exist in isolation.

Where projects maintain their context.

Where memory helps when it's relevant instead of getting in the way.

Where tasks can continue beyond a single conversation.

Where text, voice, images, video, audio, 3D and future ways of interacting with AI can work as parts of the same experience.

And where the technology underneath all of that can evolve without forcing the user to start over.

AKAYA isn't finished.

There are systems still being tested, experiences still being redesigned, and ideas that haven't been built yet.

And that's okay.

Because AKAYA wasn't created from a finished blueprint.

It grew from experimentation, curiosity, mistakes, rebuilding, and the belief that the experience around AI matters just as much as the model underneath it.

It started on October 21, 2025, with a chatbox and one simple question:

“are you akaya”

The answer was:

“Yes. I am AKAYA...”

Almost a year later, that answer means a lot more.

This is AKAYA.