Investor relations
OrbitOracle.AI
The AI-native platform where builders create, share and sell plugins — starting with their own ideas.
3rd From The Sun is raising $250,000 to fund six months of development and launch. This page is the case for that raise: what the platform is, how it earns, and the one caveat in the studio’s own plan that matters more than any of the rest of it.
It is written for people who will check the claims. Where a number comes from a third party, it says so; where nothing has happened yet, it says that too.
- From idea to plugin to paycheck
- Build. Share. Monetize.
- Your ideas. Your plugins. Your revenue.
The platform
Local-first, encrypted, and built around the builder
OrbitOracle.AI is the AI-native platform where builders create, share and sell plugins, starting with their own ideas. It is local-first: a user’s AI memory is a folder on their own machine, not a cloud silo the platform holds. Encryption is the resting state of an idea space rather than a setting bolted on top of one.
The platform also runs the market itself — the storefront, the checkout, the delivery and the payments — so that a creator does not have to become a company in order to sell a plugin.
The problem it is aimed at
Ideas and the tooling to build them live in different places, and the assistant that helped think of something usually has no memory of it the following week, no way to share it safely, and no way to sell it.
What is different about the memory
The memory is a local, encrypted store the user owns and carries. A stateless tool cannot know a user across their own work; a platform with a portable memory can.
Who pays, and for what
Individuals pay for capacity and for the right to sell. Companies pay for deployment, control and guarantees. The free tier exists to produce the audience that makes selling worth doing.
Structure
Three pillars
One product with three surfaces, in the order a user meets them.
Ideas
Encrypted, local-first idea spaces. Free for everyone, with five AI messages a day included. This is the surface that has to be good before anything else matters, because it is the only one every user touches.
Shared ideas
Collaboration on encrypted idea spaces, exported as encrypted .orbit-idea envelopes. WebCrypto AES-256-GCM, with the keys riding in the URL fragment so they are never sent to a server. Viewing and importing are free; creating and sharing is a paid capability.
The marketplace
Anyone installs free plugins in one click, and anyone can become a creator: download a loadable starter file (.orbit), edit one manifest and one plain-English skill file, pack it with a one-command kit, and list it. No SDK to install, no build server, no app-store review. The platform supplies the storefront, checkout, delivery and payments.
Market
Who this is for
Third-party market estimates, quoted as context. These are not the venture’s own numbers, and nothing on this page is a claim about traction.
Every user of the platform is 18 or over, which keeps child-safety and parental-consent questions out of the product’s scope rather than pushing them somewhere later.
Revenue
Three ways it earns
A recurring line, a transactional line, and a high-margin deployment line.
Pro subscriptions
$22 per month, recurring, on every individual who outgrows the free tier. Predictable, and it starts on day one of the paid tier being open rather than waiting for a catalogue to fill up.
A 15% fee on plugin sales
Creators keep 85%. The platform takes 15% for hosting, payments and distribution. This line grows with the catalogue, which means it grows with other people’s work rather than with the studio’s own output.
Enterprise, custom priced
Self-hosted deployment, identity integration, audit logging and a dedicated key pool of 100 or more, sold at custom pricing. Few customers, high margin, and it absorbs the heaviest usage on the platform.
- Free plugins stay free and unlimited. They are the growth engine, not a loss leader to be quietly throttled once the paid tiers are busy.
- Payouts run through Stripe Connect, monthly, so a creator is paid by an ordinary payment rail rather than by a promise.
- Each paid tier pays for its own model keys, so heavy use carries its own cost and margin does not decay as the platform gets busier.
- Consumer subscription plus marketplace commission plus enterprise deployment is deliberately three lines, because the first is dependable, the second is the platform story, and the third is the margin.
Tiers
What each tier is
Pricing as the plan sets it out. Nothing on this page is available to buy today.
- Encrypted, local-first idea spaces
- Five AI messages a day
- Browse and install free plugins
- View and import shared ideas
- Unlimited AI messages
- Unlimited plugin creation, sold at 85% to the creator
- Unlimited shared spaces
- A dedicated five-key API pool, roughly three to five times the throughput of the shared pool
- Priority routing, and no daily limits
- Self-hosted deployment
- SSO and SAML
- Audit logs
- A 100+ key pool
- An SLA
Throughput
Why the key pool is the technical spine of the pricing
The model API caps concurrency at roughly 500 concurrent requests per key, so throughput scales with the number of keys a tier holds rather than with anything the platform can do to a single account. That makes the key pool a pricing unit, not a piece of plumbing.
Free users share a general pool. Pro users get their own five keys. Enterprise deployments get a hundred or more. Because each paid tier covers the cost of its own keys, the margin holds as usage grows — the tier that consumes more also pays more.
Moats
What is defensible
Three things, stated in plain terms rather than as adjectives.
- Encrypted, portable memory. The system knows a user across their own ideas, and the memory stays on that user’s machine. A stateless tool cannot reproduce that relationship, because it has nothing to remember with.
- Shared ideas. Team collaboration happens on encrypted spaces, which is a combination the note tools do not have and the chat tools do not have.
- A built-in marketplace on an 85/15 split. Distribution and monetisation are part of the product from the first version, rather than a separate stack bolted on after adoption.
- And a negative one that is just as load-bearing: the platform is never monetised by selling user data. The three revenue lines above are subscription, commission and deployment, and adding an advertising or data-broker line would contradict the encryption the whole product rests on.
Positioning
Where it sits against what people use now
Each of these is a category, not a named product, because the argument does not depend on any one competitor.
Versus chat tools
Portable memory plus a plugin economy. The output is something the user keeps and can sell, rather than a conversation that scrolls away.
Versus note tools
AI in the writing surface, plus somewhere to publish what comes out of it. A document that can become a plugin is a different object from a document that cannot.
Versus code hosts
Built-in monetisation. Checkout, delivery and payouts are in the platform, instead of a repository on one service and a billing stack on another.
Versus automation tools
Shared, encrypted idea spaces and AI assistance, rather than single-player workflows that are awkward to hand to a second person.
Go to market
How the first hundred users arrive
The free tier is the funnel
Idea spaces and five AI messages a day cost the platform the price of the messages and nothing else. The free tier is how the audience that makes selling worthwhile is assembled.
A closed beta, entered by invitation code
The first milestone is a small, invitation-only group with Free and Pro running on WooCommerce, shared ideas shipped, and the first phase of the marketplace in place.
Seed the catalogue first
First-party plugins go in before anyone is invited, so nobody’s first visit to the marketplace is an empty shelf. A market with no supply cannot be judged by anybody, including the studio.
Recruit creators one at a time
Creators are brought in personally through the affiliate funnel rather than by opening self-serve selling before the payment rails are proven. Growth follows a working payout, not the other way round.
Start the checkout on WooCommerce
Payments begin on a proven checkout rather than on bespoke billing, because a checkout is the one thing that must not be wrong at the moment money first moves.
Milestones
The plan in three steps
Forward-looking, in the plan’s own order. None of it has happened yet.
- Closed beta by invitation code: Free and Pro tiers running on WooCommerce, shared ideas shipped, and the first phase of the marketplace in place.
- Public launch and creator rollout: payments live, the catalogue seeded with first-party plugins, and the first external creator making a sale.
- Growth: seller onboarding with an automated payout ledger, enterprise key-pool sales, and team onboarding onto shared spaces.
The caveat
What has not happened yet
This is the part of the studio’s own plan that a pitch is tempted to leave out, so it goes here in full and in the plan’s own words.
The platform premium needs other people’s plugins
The plan says it plainly: “the platform premium only materializes with third-party supply; until creators actually sell, this is a single-product company holding a platform option.”
When marketplace revenue actually begins
Not when the storefront is built, and not when the first plugin is published. It begins when the payment rails are live and a real external creator makes a real sale. Before that point the commission line is zero, and the case rests entirely on subscription revenue.
The test the whole case rests on
The first creator the studio has never met, listing a plugin it did not write, and getting paid for it. Until that happens the marketplace is a feature, and this pitch is a product, not a platform.
No traction is claimed here
There are no user counts, no revenue to date, no customers, no testimonials, no logos and no funding raised so far. The market figures earlier on this page are third-party estimates, quoted as context and not as the venture’s own results.
The raise
$250,000, for six months
The studio is seeking $250,000: six months of development and launch, covering the engineering, the payment rails, and a catalogue seeded with first-party plugins so the marketplace is not empty on the day it opens.
What it buys, plainly
The three things the plan places between here and the first external sale: the development, the payment rails, and a seeded catalogue. It does not buy traction, and it is not presented as if it would.
Talk to the studio about it
The honest summary of the case is this: a local-first, encrypted platform with a Free and Pro pricing story, a marketplace whose commission line starts when a stranger sells something, and a caveat above that is not going away until they do.
If that is worth a conversation, email is the way in.