An autonomous ecosystem for software
- Put your software online the way you post on social media
- Share your software the way you share a Google Doc
- Look after your software the way you look after your phone’s settings
- Anyone, anywhere, can do it.
How it works
This is Loisium. Walk through it.
https://your-software.loisium.liveCopy
1 / 9 Put it online the way you post on social media.
Choose your folder, the way you choose a photo. Lois tries it on a copy of your data, you press Go live, and it is out there, at its own address.
- A folder or a zip, straight from your computer
- Python, JavaScript, Ruby, Go, Java, C# and more
- A database is made for it if your code asks for one
2 / 9 Your code opens here, like in an editor.
Every file, with a line saying what it does. Start typing and a draft is made for you. Your live software is not touched.
- Saved as you type. Open a file, search the code
- Lois checks your change after you save
- Click any part of your software in the Preview to see the line of code that draws it
- Every version is kept. Any of them can be put back, read or downloaded
3 / 9 Nobody sees a new version before you do.
It runs first on a copy of your real data. Nothing leaves it: no email is sent, no payment is taken.
- Lois goes through it first: opens the pages and fills in the forms, on both versions
- What changed is outlined, the live version beside the new one
- Lois asks you only when it is yours to decide: if something of your data would be lost
- Go live when you say so. The version before is kept
4 / 9 A database of its own. Backups that were tried.
If your code asks for a database, one is made for it: Postgres, MySQL or Redis. Nobody has to set it up, and only this software can reach it.
- Your data in a table: change a value, add a row, undo
- A spreadsheet or CSV file in, the whole table out as a spreadsheet
- Each backup is put back on a spare disk, to check it really works
- Every change made here is kept in the software's history, with who made it
5 / 9 Public or private. You say who may do what.
Open your software to everyone, or put a sign-in in front of it and name the people. People sign in with Google, using the account they already have. Nothing is added to your code.
- Who can use it: the people you name use your software
- Your team in Loisium: an Editor changes its data
- An Admin also adds and removes people
- Everyone else is turned away at the door
6 / 9 Share it the way you share a Google Doc.
Type an email and press Add. They get a mail with the link, open it, and sign in with the account they already have. Nothing to install, and no Loisium account for them.
- Add by email: the invite says who shared it, and where it opens
- Anyone at your company: everybody with a Google Workspace account at your domain
- Someone leaves: once the company switches their account off, they are out
- Remove a person and they are refused at once
7 / 9 See who came, and what went wrong.
Loisium measures visits to your software for you: never a name, never anything anyone types, never shared. Nothing to install.
- People, who came back, pages opened, where they came from, in graphs
- Logs kept across restarts, and you can search them
- Problems first: how many times, and since which version
- Passwords, keys and card numbers are hidden before anything is kept
8 / 9 Look after it the way you look after your phone's settings.
One Settings page, in plain words: the keys your software needs, and who at Loisium may look at its data. Its packages are checked again every day, by Lois.
- Known holes are named, package by package
- Known malware keeps a version from going live
- Loisium reads your code and tells you which settings it asks for
- A key can be made write-only: nobody can read it back, not you and not Loisium
9 / 9 Scan your software the way your phone scans for viruses.
Lois checks eight parts of your software and ticks each off as it finishes. Each one gets a word: Fine, Lois is on it, or Needs you.
- The whole software, every file and every package
- No score to puzzle over: a plain word for each part
- It says what it does not check, too
The problem today
Writing software got easy. Running it did not.
AI tools let anybody make software now. Keeping it online is still a job for an engineer.
Today Many separate tools: one to host it, one for the database, one for logins, others for backups, logs and visitors.
With Loisium One place. Hosting, a database, logins, backups, logs and visitors are built in.
Today Each has its own sign-in, its own bill and its own way of working.
With Loisium One sign-in, and one place to look.
Today They are made for engineers. The words alone stop most people.
With Loisium Plain words. Loisium reads your code and sets it up itself.
Today Adding logins and who-can-do-what means changing your code.
With Loisium You say who may do what on a screen. Your code is not touched.
Today When it breaks at night, nobody is looking, and you find out from a user.
With Loisium Lois checks it every minute, day and night. When it stops Lois starts it again and tells you what was done.
Today A new version goes straight to your users, and you hope.
With Loisium You see it first, on a copy of your real data.
Job by job: what the tools do today, and what Loisium does.
Putting it online
Most platforms today
Most hosting services build your software from a code repository you connect, or from a tool you install on your computer.
Every change you send usually goes live at once. Nobody asks you first.
With Loisium
Upload a folder. It goes live when you say so.
Upload your code as a folder or a zip. Loisium works out how to run it and gives it an address with https.
New code you upload waits for your Go live. Until the new version answers, your visitors keep the one before.
Its own database
Most platforms today
You usually sign up to a separate database service, make the database, and copy its address into your hosting settings yourself.
With Loisium
Made for it, the moment the code asks.
If your code needs Postgres, MySQL or Redis, Loisium makes one and hands your software its address. Nothing to sign up to, nothing to copy.
Each database has its own login, and only this software can reach it.
Sign-in, and who may do what
Most platforms today
A sign-in service means adding its code to your software.
Who may only look and who may change things is then checked in your own code. One mistake there, and the wrong person gets in.
With Loisium
A door in front of it, with nothing added to your code.
Name the people. They sign in with an account they already have.
Who may use it is checked at the door, before your software sees the visit. Everyone else is turned away, and a person you remove is refused at once.
Backups
Most platforms today
Databases on paid plans are usually copied every day. On free plans, often not at all.
Whether a copy can really be put back, you find out yourself, usually on the day you need it.
With Loisium
Every copy is put back, and checked.
A copy of your files and databases is taken every day, and one more before each new version goes live.
Each copy is put back and checked, then marked Tested.
When it breaks at night
Most platforms today
The hosting service starts a crashed program again. If it keeps crashing or runs out of memory, that is yours to fix, often by paying for a bigger size.
A monitoring tool can wake you with a call at 3 a.m. Then somebody has to fix it.
With Loisium
Lois deals with it, and tells you later.
Lois checks every minute. When your software stops, Lois finds out why. If it ran out of memory, Lois gives it more, starts it again and watches that it stays up.
When you next open Loisium, Lois says what happened, in a few lines.
Packages with holes
Most platforms today
A package checker reads your code and suggests an update. Some warn you about known malware too.
You read the update, test it and put it live yourself.
With Loisium
Checked every day, by Lois.
Every live piece of software is checked again every day against the lists of known holes and known malware, package by package.
A new version carrying known malware is stopped before it goes live.
Visitors
Most platforms today
A visitor counter is one more service: an account to open, and a script to add to your pages.
With Loisium
Counted for you. Nothing to add.
Loisium counts the visits for you: people, who came back, pages opened, where they came from.
It never keeps a name, and never reads what anyone types. On public software it sets one cookie, holding a random number and nothing about the person.
Logs
Most platforms today
Hosting services keep recent logs only: an hour, a week, or a few thousand lines.
To keep them longer, search them or count each error, you usually add another service and its code.
With Loisium
Kept, searchable, problems first.
What your software writes is kept across restarts, and you can search it.
What went wrong comes first: how many times, and since which version. Passwords, keys and card numbers are hidden before anything is kept.
Who did what
Most platforms today
A record of who changed what is usually on team or enterprise plans only.
Whether a line of it can be changed afterwards is seldom said.
With Loisium
Written down, and kept as written.
Every change to your software, who made it and when: you, your team, Lois, or somebody at Loisium.
A line cannot be quietly changed or removed. It would show.
Trying it before it goes live
Most platforms today
A preview copy usually starts with an empty or sample database, not your real data.
To have its pages opened and its forms filled in, somebody writes test scripts and keeps them working.
With Loisium
Lois presses the buttons first.
The new version runs on a copy of your real data. No email leaves it and no payment is taken.
Lois opens the pages and fills in the forms, on the version before and the new one, and shows you what changed.
Your own domain
Launching soon
Mail
Launching soon
Jobs on a schedule
Launching soon
File storage
Launching soon
A status page
Launching soon
Team secrets
Launching soon
Being found
Launching soon
The big companies have their clouds. Smaller software has Loisium.
Large software Big companies run on AWS, Azure and Google Cloud, with a team of engineers to run them.
Your software Smaller software has Loisium: the same kinds of things, in one simple place, with its engineer already inside.
Large software Built for teams of engineers.
Your software Built for the person who made the software.
Large software You choose, connect and watch many services yourself.
Your software You upload it. The rest is already there.
Large software Your own engineers look after it.
Your software Lois looks after it, day and night.
That engineer is Lois.
All of it is run by Lois, your AI engineer. With your software, day and night.
Lois is the engineer inside Loisium: learns what is normal for your software, sees what is coming, and deals with what breaks.
You do not have to watch it, and you do not have to be afraid of it.
Sees it coming.
Every hour Lois looks at where things are heading, and tells you before a limit is reached: what fills, by when, what your visitors would notice, and what can be done.
At this pace your software's database fills its room in about 9 days.Lois, under "What Lois sees coming"
Deals with what breaks.
Lois checks every minute. When your software stops, Lois finds out why, gives it what it needs and starts it again, then looks whether it stayed up.
It ran out of memory. Lois gave it 1 GB (it had 512 MB) and started it again.Lois, under "What Lois did"
Tells you plainly.
When you open Loisium, Lois says what happened while you were away, in a few lines, and asks you only for what only you can give.
Your software needs PAYMENT_SECRET_KEY. Only you have it — paste it here.Lois, when a setting is missing
And many more.
Small things you would not think to ask for, already there.
- Who did whatEvery change to your software, who made it and when. A line cannot be quietly changed or removed: it would show. Complete — nothing changed or removed.
- Any version, backEvery version of your code is kept. Any of them can be put back.Live Version 4
- It rests when nobody uses itSoftware on the free plan that nobody opens for a week goes to sleep. It wakes by itself when somebody comes.
- What Lois sees comingTold before a limit is reached: what fills, by when, and what can be done.At the pace of the last days, nothing reaches a limit within the week.
- Nobody at Loisium reads your data without asking you firstWe ask, you allow it for an hour or say no, and the look is written into your history.Allow for 1 hourDeny
- Not sure what something is? Drag Lois onto it.Lois tells you what it is, what it is for, and what is happening there right now.
- Deleted by mistake?For 5 days you can bring your software back exactly as it was.
Loisium is not finished, and it says so. Launching soon
Our team is building these right now, and they will be ready for you soon.
- Asking Lois Write to Lois and ask about your software. Today Lois tells you what happened, and cannot be asked yet.
- Your data in plain English Ask for your data in your own words and get the rows back, without writing a query.
- Your own domain Your software at an address of your own. Buy one inside Loisium or bring yours, and Loisium sets up everything behind it, the records and the padlock, with no other site to visit.
- Mail Mail addresses on your own domain, and the mail your software sends. Loisium sets it all up, with no separate mail service and nothing to copy by hand.
- A weekly report from Lois Once a week Lois writes to you with how your software did: who came, what Lois did, and what is coming.
- Jobs on a schedule A piece of your software that runs at set times, every night or every hour, with nothing else to rent.
- Building with your own AI Connect the AI tool you already build with, so it works on your software here: in a draft, with your Go live before anything changes.
- Being found For software open to everyone: Lois makes what search engines and AI search need to find it, and walks you step by step through what only you can do. Lois remembers it all, so you can ask about it later.
- File storage Somewhere for the photos and PDFs your software keeps.
- A status page A page where your visitors can see whether your software is up.
- Team secrets Keys that belong to no single piece of software, shared with the people you choose.
FAQ
What people ask before they start.
Short answers, in plain words. Anything else: founders@loisium.dev
What is Loisium?
Loisium is a new, simpler home for your software — an autonomous ecosystem that runs it for you. Put your software online the way you post on social media. Share it the way you share a Google Doc. Look after it the way you look after your phone’s settings. Hosting, a database, sign-in, backups and logs are already inside, and Lois, an AI engineer, watches over it day and night. You don’t need to be technical to use it.
Do I need to know coding or servers?
No. You bring the code, written by you or with an AI tool. Loisium reads it, works out how to run it and sets it up. There is no server to rent. When your software needs something only you have, like a payment key, Lois asks for it in plain words.
What kind of software can I put on Loisium?
Small-scale software: a website, an online tool or an API that people open in a browser — the kind a small business, a startup or one person builds. Python, JavaScript, Ruby, Go, Java, C# and more all work, and if it needs a database, one is made for it. Loisium is built for small-scale software today, not for large systems with many servers. Software written for MongoDB has to bring its own database for now.
Do I need GitHub?
No. Upload your code as a folder or a zip, straight from your computer. You need no account anywhere else.
How much does it cost?
Nothing during the beta: it is free, one piece of software each. Plans come later, and we will tell you before anything changes.
Are my code and my data safe? Who can see them?
Your software is open only to the people you add, unless you choose to open it to everyone. Its database has its own login, and only your software can reach it. Your .env file is never kept with the code, and a key can be made write-only: nobody can read it back, not you and not Loisium. Nobody at Loisium reads your data without asking you first, and every look is written into your history.
What happens if my software breaks?
Lois checks it every minute, day and night. When it stops, Lois finds out why, gives it what it needs, starts it again, and tells you what was done. A new version is tried on a copy of your data first, and every version is kept, so an earlier one can be put back.
Can I take my code and data with me if I leave?
Yes. Every version of your code can be downloaded from its page, and every table of your database comes out as a spreadsheet.
Bring what you made. Free during the beta, one piece of software each.
The beta runs on one server. If it is full when you arrive you join a waiting list, and we tell you why and what your place is.
Plans come later. We will tell you before anything changes.