Loom
Threads into cloth.
Your source control, your wiki, and documentation that builds itself from what you push — on servers we have run for years.
Plain and proven
Loom runs on servers we have operated for years — the same machines that have carried our own work and our customers' since long before any of this had a name. They are reliable and they are plain. One server, doing its job, with its backups taken.
Two things Loom does not do, said plainly so you are not surprised later. There is no automatic failover — if a machine goes down we bring it back up; a second machine does not take over in the same second. And Loom is not built for regulated work. If HIPAA, FERPA or GDPR govern what you do, Foundation is your door, not this one.
If neither of those is your situation, Loom is a great deal of capability for very little ceremony.
Take what you need
Three products, named for what they are. Backup is included in every one of them.
git
Gitea
Private source control. Every version of your work and a record of who changed what, when.
wiki
JSPWiki
A wiki your team writes in — procedures, decisions, and everything that would otherwise live in one person's head.
easydoc
Gitea, JSPWiki and EasyDoc
Everything above, plus documentation that builds itself from the code you push.
Want source control and a wiki but not the documentation layer? Contract for both — there is no bundle to work out.
easydoc
Push your code. That is the whole of what you have to remember.
EasyDoc reads what you pushed and builds the documentation from it — checking that the contracts between your programs still hold and publishing a site for each group that should see it, showing them only what they have access to.
It is the part people do not expect to enjoy. They do.
Backup is not something you buy here
It is on.
We pull the copy from your server rather than letting your server push it to us, so a machine that has been compromised cannot reach its own backups. Databases are dumped properly rather than copied while they are running — the difference between a file you can restore and a file that merely looks like one.
Each copy carries a manifest describing how to rebuild the machine from it, and we have done that rebuild on our own systems rather than only taking the copies and hoping.
Tell us what you need running
Source control, a wiki, documentation that keeps itself current, or all three. Tell us what you are working on and we will tell you what it takes.
Get in Touch