in a box · One engine, a whole fleet of software products
One engine mints a whole fleet of software products -- one per brand, not one fork per product.
in a box is the method behind a growing fleet of distinct .software products that already run on one shared engine. Each product is its own brand, its own theme, its own domain -- pointed at the same engine through config, not forked into a separate codebase. That is the factory: not a copy machine, one engine minting many products. This page is honest about what runs today and what is still being built.
{thing}.inabox.software — the fill-in-the-blank cue is the vision the running fleet already proves by hand. The self-serve version is being built; it is not live on this page.
Pre-launch, early access. No card charged today. Every capability below is labelled built or building honestly.
How the factory works
Config plus theme plus domain, over one engine
The factory is config plus theme plus domain over one engine, not a fork per product. A new product is a new configuration of the same running engine -- a brand, a theme, and a domain -- so a fix or a feature on the engine reaches every product at once, instead of drifting across a drawer of separate codebases.
Configure a product
A product starts as a configuration on the shared engine -- a name, an audience, and the surfaces it turns on -- not a new codebase copied and edited by hand.
Theme it as its own brand
Each product wears its own brand: its wordmark, its palette, its voice. The engine underneath is shared; the face is distinct, so a visitor sees a product, not a template.
Point a domain at the engine
The product gets its own domain, dispatched to the one engine by host. That is how a fleet of distinct .software front doors runs on a single running codebase today.
Ship on the engine everyone shares
Because every product is the same engine configured differently, a fix or a feature lands once and reaches the whole fleet -- no per-product drift, no forgotten fork left behind.
What in a box has built, and what it is building
The shared engine, the live fleet of products on it, and the digital rent-or-own eReader are built and running today. The self-serve spin-up and live billing are building -- switch-flip-ready, and named plainly as not live yet.
Built
One engine, minted many ways
Every product in the fleet is the same engine, configured differently -- a brand, a theme, and a domain over one running codebase. A new product is a new configuration, not a fork, so an improvement to the engine reaches the whole fleet at once instead of being re-implemented per product.
Built
A live fleet of owned .software products
The operator already runs a growing set of distinct-brand .software product front doors, each on its own domain, all served by the one engine. Every sibling product is a real instance this method produced. The fleet is running today; the number is not printed here because we do not fabricate a count.
Built
Digital rent-or-own eReader, read in your browser
One product in the fleet delivers real digital book editions: rent or own an edition and read it in your browser, with your own library of what you took. The reader and the library surfaces are built and running. Money is honest-off here -- no price is shown on this front door.
Built
Config plus theme plus domain, not a fork
The factory method itself is the built thing: a product is defined by its configuration -- what it is called, how it looks, and where it lives -- pointed at the shared engine. This is why the fleet grows without a codebase per product, and it is proven every time another front door goes live on the same engine.
Building
Self-serve spin-up: fill in the blank
The vision is the fill-in-the-blank cue: name your product, pick a theme and a domain, and spin up your own front door on the engine. That self-serve path is being built. It is not live on this page -- you cannot generate a new product from here yet, and this page does not run a live generator. The method it automates is the same one the running fleet already proves by hand.
Building
Live checkout and billing
Turning a product into a paid subscription is being built and is switch-flip-ready. It is not live today: no card is charged anywhere on this page, no price is shown, and no field here can turn a charge on. When billing is real for a product it will be labelled real, and the price is set in a conversation, never on this front door.
The fleet
A real, growing fleet of .software products
The fleet is real and already running: a set of distinct-brand .software product front doors, each on its own domain, all served by the one engine. Every sibling product is an instance this method produced by hand today. We do not print a product count on this page -- the honest claim is that the fleet exists and is growing, not a fabricated number.
One product in the fleet already delivers real digital books: rent or own a book edition and read it in your browser, with your own library of what you rented or bought. The read surface and the library are built and running. Money is honest-off on this page -- no price and no checkout is shown here; what a book costs is set on the product itself, never on this front door.
Where in a box is today
Pre-launch, and honest about it
Early access, pre-launch: this front door is live, and so is the fleet it describes. The self-serve path where you spin up your own product, and live billing, are being built and are named plainly as not live yet. Nothing on this page is charged, and nothing here claims to run before it actually does.
Honesty and money
What is true today, stated plainly
Money is honest-off across this whole page. No price and no dollar figure is rendered anywhere, no card is charged, and no field on this page can turn a charge on. Live billing is being built and is switch-flip-ready; when it is real it will be labelled real, not before.
Built means built, building means building
Every capability on this page is labelled honestly. The fleet and the eReader delivery are built and running. The self-serve spin-up and live billing are building -- switch-flip-ready, and never claimed as live before they are.
No card charged, no price on this page
Money is honest-off: no price or dollar figure is rendered anywhere here, no card is charged, and no field on this page can turn a charge on. Live billing turns on for a product only once it is truly wired.
No fabricated numbers or names
We do not print a product count, a customer name, a testimonial, or an adoption stat on this page. The honest claim is that the fleet exists and is growing, and that the eReader delivery is real -- not an invented figure.
Minor data is consent-gated if it is ever relevant
If any product on the engine ever captures information about a minor, that data is consent-gated by default and never made public by default -- the same default-deny posture used everywhere else on the platform.
FAQ
Common questions
Is inabox a live factory I can use to make my own product right now?
Not yet. The self-serve path where you spin up your own product front door is being built and is named plainly as not live. What is real today is the method itself: a growing fleet of distinct .software products already runs on one shared engine, config plus theme plus domain, not a fork per product. This page does not run a live generator.
What does built versus building mean here?
Built means the substrate is live and running today -- the shared engine, the fleet of .software products on it, and the digital rent-or-own eReader delivery. Building means switch-flip-ready but honestly not live yet -- the self-serve spin-up and live billing. We would rather say plainly what is on than imply more than the product does.
Is the fleet real, and how many products are there?
The fleet is real: a set of distinct-brand .software product front doors, each on its own domain, all served by the one engine. We do not print a count on this page, because a fabricated number would not be honest. The claim is that the fleet exists and is growing.
What is the eReader, and can I actually read a book?
One product in the fleet delivers real digital books: you can rent or own a book edition and read it in your browser, with your own library of what you took. The reader and the library are built and running. Money is honest-off on this page -- what a book costs is shown on the product itself, never here.
Does it cost anything, and is a card charged?
No card is charged on this page, and no price is shown anywhere on it. Money is honest-off: live billing is being built and is switch-flip-ready, and no field on this page can turn a charge on. When billing is real it will be labelled real, and any price is set in a conversation.
Is inabox a separate company from the products it runs?
No. in a box is the method and the engine the operator uses to run its own fleet of software products. It is a distinct front door for that method, not an independent company, and it is operated by the same team behind the products it describes.
What happens when the self-serve spin-up is ready?
When the self-serve path lands it will be labelled built, not before -- the same honesty rule every capability on this page follows. Until then the method is proven by the fleet already running, and the honest next step is a conversation, not a checkout.
Get in touch
Tell us what you want in a box
The engine is real and the fleet is running. Talk to us about the product you have in mind and we will tell you honestly what is ready today and what is still being built. No card is charged today, and no price is shown on this page.