What WYTOR is

WYTOR is the company I am building to hold the work I have been doing for years under my own name: software products, applied AI research, and systems built for other businesses. The name comes from Vitorio, my father’s third name. The line under it, Build Beyond, is the instruction.

Why a company, and why now

For most of the last two years I shipped as an individual. Seven apps went to the stores in one stretch. One paper got through peer review at ICANN 2026 and sixteen more are under review or sitting as preprints. A wedding-planning product grew a vendor network and an AI concierge. None of that had a legal home, a shared bank account, or a clear owner for the intellectual property. The company fixes that. The company is being incorporated in Goa, India, under the proposed name Wytor Technologies; the name application went to the Ministry of Corporate Affairs on 6 November 2026.

What WYTOR is not

It is not an AI agency. It is not an app studio that builds whatever walks in. It is not a collection of unrelated side projects with a logo on top. Those are all easier to explain and all wrong.

What it is

Three things, each feeding the other two.

Products and ventures. Celabe, Amorelle, Nourish, Billfold, Oravira and the rest. Each one is a bet that a specific group of people has a problem worth paying to solve. Each one is listed on this site with its real status, because a prototype called a product is a lie that catches up with you.

Research and engineering. Measuring things properly: latency in production voice pipelines, how language models fail by severity, where a person’s eye lands first on a page. The research pays twice, once as a paper and once as a capability the products and the enterprise work can use.

Systems for businesses. AI agents, knowledge systems, integrations and the software around them, built for companies with operational problems and budgets, with acceptance criteria written down before any code.

The one rule

Every creation should strengthen our ability to create again. A product should leave behind a reusable component, a dataset, a distribution channel, or a lesson written down. A research result should become a capability. An enterprise project should become a template. If something we build makes the next thing harder, it was the wrong thing to build.

What happens next

The site you are reading is the first public version. The company is being incorporated. The first enterprise conversations are starting. If you have a problem that fits, the enterprise page explains how an engagement runs, and the contact page is one step away.