Aubia Starts With a Waitlist

You can join a waitlist on aubia.dev. The home page has no pricing table, account registration or download.

I've already defined the desktop application's modules and its end-to-end user journey. Aubia is a cockpit where AI agents from several providers review each other's work. Before launching it, I want to know whether other developers share the same frustration: working with several agents in turn, without being able to have them talk to each other. The Creator's letter explains where that need comes from.

I call this period of preparation for launch Phase 0. The site collects the first signups for beta 0.1.

Signup takes two steps, following the double opt-in process. You enter your email address, then click the link in the email you receive to confirm it. Without that click, the signup remains pending until it is deleted. The dedicated article covers this process in detail.

A Single Action Available

The public pages are available in six languages. Each version has its own URL with a language prefix and can be indexed separately by search engines.

A Single Write Route

The form sends signups to aubia.cloud. This is the site's only write route, declared in the same group as the home page.

Route::prefix('{locale}')
    ->where(['locale' => implode('|', SupportedLocale::values())])
    ->group(function (): void {
        Route::inertia('/', 'welcome')->name('home');

        Route::post('/waitlist', [WaitlistController::class, 'store'])
            ->name('waitlist.store')
            ->middleware('throttle:waitlist');
    });

This excerpt shows only those two routes. The group also includes the two legal pages, the confirmation and unsubscribe pages, and this blog. The site has no dashboard or members' area.

No Disabled Buttons

I could have added "Download" and "Create account" buttons, grayed out and labeled "Coming soon". I'd rather the page offer an action you can take immediately.

Account registration isn't open yet on aubia.cloud, and the desktop application's binaries aren't signed. Those buttons would have nowhere useful to lead.

They're planned for Phase 1, the launch, along with feature pages, pricing and downloads. That stage depends on signing the binaries and opening account registration. I'm not announcing a date yet.

A Domain for Each Purpose

The public website and emails use aubia.dev. The cloud application and its API are hosted on aubia.cloud. The aubia.app domain is reserved for the desktop application.

The public website has separate infrastructure from the cloud application. When you enter your email address on aubia.dev, the site forwards the signup request to api.aubia.cloud.

No personal data is stored long-term on the public website, which runs with no local database. Redis temporarily stores hashes of the email address and IP address to limit the frequency of requests.

Measuring Without Cookies or a Banner

I need to know whether visitors see the form, sign up or encounter an error. Fathom Analytics measures this journey without cookies or individual tracking, so no consent banner is required.

Nine events track when the form enters the viewport, submissions and their outcomes, any errors, confirmation success or failure, and when the signup counter is displayed.

The counter fetches its total server-side from aubia.cloud. It counts confirmed signups: those from the form, after clicking the link received by email, and the invitations I record myself, confirmed without that click. Addresses awaiting confirmation are excluded.

The number is displayed only once it reaches a certain threshold. This choice to limit the information shown is consistent with the product's vision.

With the Beta, Aubia Will Leave My Machine

Beta 0.1 will ship first on macOS Apple Silicon, with Linux and Windows following in 1.0. You'll use it on your own projects, with your own API keys (BYOK).

That's where I'll see how Aubia fits into a working day.