Selling to the world should not depend on where you were born.

You wrote a good product, and then the checkout page stopped you because of the country you live in. AuroraSky exists for that. We buy the developer's software license, resell it worldwide under our own name and pay the developer the license fee. We are the merchant of record for the sale: we take on the collection, the invoice and the tax. The developer stays on the product.

Merchant of record model
We sell under our own name
Not accepting transactions yet

01Model

We are the merchant of record.

Kervan LLC buys the developer's software license. The customer buys the product from Kervan LLC: Kervan LLC collects the money and Kervan LLC issues the invoice. Being merchant of record is not a label; it is a transfer of responsibility, and the tax and compliance burden stays with us.

Kervan LLC buys the license.
Kervan LLC sells to the customer and issues the invoice.
Dispute risk stays with us, not with the developer.

02License fee

We pay the developer the license fee.

Because we buy the license from the developer, we owe them a license fee. We pay it to the developer's own bank account on the schedule set in the agreement. The license fee is our own debt to our supplier; it is not a balance we keep for the developer.

The license fee is paid to the developer's own bank account.
The license fee is our own debt to our supplier.

03Accounting

When recording money, correctness comes before speed.

Every movement of money is recorded with double-entry accounting: debits always equal credits. Amounts are kept as integer minor units, so rounding differences cannot appear. If the same notification arrives twice, it is not processed twice — a customer is never charged twice. No money logic is written before its test is.

Debits always equal credits.
Integer minor units; no rounding drift.
A repeated notification is not processed twice.

04Refunds and disputes

Refunds and disputes are not a patch bolted on later.

The hard part of selling is not taking money; it is giving it back. Refunds and disputes have been working parts of the system from day one, and they follow the same rule as every other entry: each movement is written on both sides. Because we are the merchant of record, we are the ones facing the dispute.

Refund and dispute flows are working today.
As merchant of record, we face the dispute.

How it works

Four steps for the developer.

01Sign-up and identity checkThe developer registers and goes through identity verification (KYC). Being merchant of record requires being able to verify the developer whose license we buy.
02API keyThe developer generates an API key in the dashboard and connects it to their own site.
03The saleThe customer buys the product from Kervan LLC and pays by card. Kervan LLC collects, Kervan LLC invoices, and the movement is written to the double-entry ledger.
04License feeKervan LLC pays the license fee set in the agreement to the developer's own bank account.

Where we stand today

We are not accepting transactions yet.

Whether a product is ready to launch is decided by its list of gaps, not by its marketing page. Ours currently looks like this:

The license fee payment connection is not wired yet.
The system records how much license fee we owe each developer; the piece that actually makes the payment is not written. Launching like this would mean making sales and being unable to pay what we owe our suppliers.
The US tax number (EIN) is pending.
The company account depends on it. Until it arrives there is no real money movement; everything so far ran in a test environment.
The legal documents are being prepared.
We do not accept transactions before the Terms of Use, the Privacy Policy and the merchant of record agreement are complete.
Document upload is closed.
A seller can enter document details, but the file itself is not stored yet.

This page will be updated as the list gets shorter. Hiding it while it is long is the fastest way to make the short version worthless.

Ask for early access.

We keep a short list of people to notify when early access opens. No form, no tracking; one address.

Ask for early access

Answered by the person who builds it.

The other product: Mira AI →