You can try Ekso:
Fully self-hosted, dockerized.
We made the pricing reasonable -- YMMV.
377 karma · joined July 7, 2011
firstname-at-lastname-dotcom
Fully self-hosted, dockerized.
We made the pricing reasonable -- YMMV.
Causal [1] seems to be another option (they also raised funding recently).
I started this a while ago and maybe it helps you:
In fact, it gets tricky as you have "location-flagged" functionality depending upon Cloud or Self-hosted.
We did this from scratch @ Documize by making (bold?) choices around deployment/runtime and database schema design for both SaaS and self-hosted "products":
- run the exact same binary (we used Golang)
- share/use the exact same database schema
- data migration process the same for schema changes
- support multi-tenanting: "enterprise" self-hosted also multi-tenanting so different teams/departments internally get different URLs
- use the same "build" process to compile and ship
Probably plenty more I could tell you!
(It's my start-up.)
Thankfully PCB was QMK and VIA compatible so nice GUI to flash the firmware with my desired keyboard layout.
Open source core supporting WYSIWYG, Markdown, Code and more.
It's built with Go and EmberJS.
* Designed for tech and non-technical user alike
* Cloud or self-host (single binary deployment)
* Open source core
* Markdown, WYSIWYG with open sourced "connectors"
* Built-in approval and versioning capabilities (no paid add-ons required)
* Secured for internal and external participants
* Opinionated content organization approach
Multi-tenanted single codebase supporting both SaaS and self-host (Windows, Linux, macOS).
Stack:
- EmberJS front-end
- Go backend (static binaries that embed EmberJS GUI)
- MySQL database
- AWS EC2 pulling Docker images from Docker Hub
Seems to work well so far.
For self-hosting try https://github.com/documize/community -- WYSIWYG or Markdown, integrate data from Trello, GitHub, or roll your own integration.
Still early days yet, but you should get a feel for docs/wiki/SaaS data embedding.
The gotcha? Runs on Windows Server which probably doesn't compute for startups but works well for typical enterprise shops that have stacks of Windows Server.
Self-hosting is still a huge market but one that is more and more under-served.
We compete routinely with Jira and win deals by providing fully loaded 50mb zipped solution that runs on Windows servers, integrates with AD/Outlook/Exchange, etc., custom Apps Framework and obligatory RESTful API. Just the things that "demanding enterprises" look for.
No idea if this helps you.
We compete with Atlassian Jira, Rally, etc. and have taken the time to craft a different UI/UX:
Hence pricing SaaS to sit below team credit card spend limit helps.
That's when polished, 'tasteful' and usable software should win.
Terrible state of affairs!
Also see my comment below.
I see a lot of comments around Word being not the right format for "distributing, sharing, commenting".
My startup Documize [1] is just a week old and is currently being tried out by a handful of legal professionals and the like for handling what happens around structured documents.
The premise is that MS Word is where structured documents are born in the enterprise world. It's what happens after they come into being that is the problem: network drives, file sync folders, email tennis, Word-track-changes, manual consolidation, etc.
A real pain.
Documize aims to help people distribute documents, collate feedback, provide version control and even allow for private notes. From a browser.
Working towards that vision at the moment -- just thought I'd throw this out there.
The funny thing is regular business users think of it as a wiki. Me and you know different!
Think of the business folks at Wells Fargo or any other larger enterprise. They will upload 100's if if not 1000's of documents. Now they can link between documents or just work on each document as they do.
Wiki is a word we think doesn't fit -- but we keep running into it.
The joy of start-ups: too much uncertainty!
For SaaS:
- freemium plan for 1 user - paid plans based upon number of users
On-premise:
- download and install core product - enterprise features like AD auth, redacting, workflows are paid for
We plan to put the core product source code onto Github so anyone can have their on hosted "wiki".
Hope this makes sense.