Founder & CEO, Jeity
For more than a decade, I worked in software engineering, building applications, designing systems, solving technical problems, and helping turn ideas into working software for other companies.
I learned a lot from that experience. Every project came with different requirements, challenges, and decisions. Some were straightforward. Others required looking beyond the immediate problem and thinking carefully about how a system would work, scale, and evolve.
But after years of building software for others, I wanted something different.
I wanted to build something of my own.
Not just an application to deliver and move on from, but products I could continue developing, improving, and growing over time. I wanted to make long-term decisions about their direction, take responsibility for what happened after launch, and apply everything I had learned to something I was building for the future.
That desire became one of the main reasons I started Jeity.
From building projects to building products
Software engineering has taught me that delivering a working application is only part of the journey.
Requirements change. Technologies evolve. People discover new ways of using software. And sometimes, decisions that made sense early on need to be reconsidered as a product grows.
I’ve always valued building systems with those realities in mind.
Working on applications, architecture, infrastructure, and technical leadership helped me understand the importance of maintainability, thoughtful design, and long-term responsibility.
But when you’re building software for another organization, the direction of that software ultimately belongs to them.
I wanted the opportunity to make those decisions for products of my own.
I wanted to build something, learn from how it works in practice, improve it, and continue that process for years rather than treating delivery as the end of the journey.
That’s the opportunity I see in building a product company.
Why I started Jeity
I founded Jeity to develop, own, and operate software products and technology platforms.
The distinction matters to me.
Jeity isn’t intended to be primarily a company that takes on unrelated development projects. I want our own products to be at the center of what we do.
That doesn’t mean client solutions or custom development aren’t valuable. They solve real problems, and Jeity may explore opportunities to build business solutions Powered by Thraia.
But I want those engagements to build on our own technology wherever appropriate, rather than becoming the entire identity of the company.
My ambition is to create products that continue evolving, serving new needs, and improving through experience.
I know that won’t happen overnight. Building a company is very different from building an application, and there is still plenty for me to learn.
But that’s part of what makes this journey worth pursuing.
Why platforms?
I’ve always been interested in what happens when software becomes a foundation for other possibilities.
An application might solve one particular problem. A platform can provide the underlying capabilities for many different applications, workflows, and integrations.
That introduces different engineering challenges. You have to think about flexibility, dependencies, extensibility, and how the system might evolve beyond its initial use cases.
One principle I want to carry across Jeity is that our products should be capable of operating independently while becoming more useful when appropriately integrated.
I don’t want every product to depend on another just because they belong to the same company.
Each should have a purpose and stand on its own. When connecting them creates real value, that integration should be possible without sacrificing their independence.
Provider neutrality, portability, and maintainability are also important design priorities for me.
These are principles we’re working toward and must continue proving through implementation, not claims that we’ve already perfected them.
Where we’re starting: Thraia and Theron
Our first two flagship platforms reflect different parts of that vision.
Thraia is our AI agent platform, currently in Alpha. We’re building it around contextual intelligence, configurable capabilities, tools, integrations, and governed workflows.
What interests me about AI isn’t simply having another model that can answer questions. It’s exploring how intelligence can work with context, interact with systems, and help people accomplish tasks while maintaining appropriate human oversight.
Thraia is still evolving, and its broader vision extends beyond what is available in Alpha today.
Theron, currently In Development, approaches technology from a different direction.
Its origins are in connected devices and IoT, but its vision has expanded toward distributed application and workflow execution across compatible edge, cloud, and self-hosted environments.
I see opportunities for these platforms to complement each other eventually, but they are intentionally independent. Any integration between them remains a future possibility.
Neither platform represents a finished destination. Both are starting points for technology we intend to continue developing.
Making room for new ideas
Not every idea needs to become a product immediately.
That’s part of why we’re establishing Jeity Labs, our initiative for exploring ideas, experimenting with technology, and evaluating potential future products.
I want us to have room to ask questions, try approaches, discover limitations, and sometimes decide that an idea isn’t worth pursuing further.
Experimentation is valuable even when it doesn’t result in a product.
And when something does show promise, I’d like us to have the engineering foundation and experience to explore it properly.
Building something for the long term
Starting Jeity doesn’t mean I’ve stopped being an engineer.
If anything, my engineering background is a major part of how I approach building the company.
I care about how things are designed, how they’re implemented, and whether they can be maintained as requirements change.
But I’m also learning to think beyond the technology itself: about products, the people who will use them, the teams who will build them, and the decisions that will shape the company over time.
Jeity is still at the beginning of that journey.
There are things we’re building, things we’re testing, and plenty we haven’t figured out yet. I’d rather be transparent about that than pretend we’re further along than we are.
What matters to me is continuing to make progress and building technology we can stand behind.
What’s next
I want this blog to be a place where we share more than announcements.
We’ll write about engineering decisions, lessons learned, experiments, product developments, and the challenges that come with building our own platforms.
Some posts will be technical. Others will be about products, ideas, or the company itself.
I hope that, over time, these stories will show how Jeity grows—not just through what we release, but through what we learn along the way.
After years of building software for others, I’m excited to be building something of our own.
And this time, the goal isn’t simply to finish building it.
It’s to keep making it better.
Building technology for what’s next.