Upd4ting (@Upd4ting) header
Upd4ting (@Upd4ting) profile picture

CTO & co-founder @AntelopeJS. Building an open-source back office your coding agent writes for you.

Belgium
Joined January 2015
Photo by Upd4ting (@Upd4ting)
Replying to @MaximeWesthoven
@MaximeWesthoven and I have been building this for years without saying a word. It started at our service company. Almost every client needed a back office, and no two were alike, so we kept building them by hand. Then a shared base. Then every fix had to be carried over to every client, one by one. AntelopeJS came out of that grind. It's run in production for our clients for a long time. Nobody outside ever saw it. Showing your work is hard. There's always one more thing to fix first. At some point you have to let people see it, flaws and all. So here it is. Open source, all of it. I'd love your honest feedback. 👇
Your ERP runs on Postgres. Your CRM on MongoDB. The shop grew on its own. Three good programs, and none of them talks to the others. Meet AntelopeJS DMS: connect the databases you already run, and get one back office on top. Open source.
2
9
13
235
We just shipped two payment modules for AntelopeJS: Mollie and Checkout.com. They sit behind the same payment interface as Stripe. Your code calls the interface, and the module you install decides who takes the payment. Changing provider means installing another module, not rewriting your checkout. Mollie also handles subscriptions. Checkout.com handles payments, and renewals go through our payment-subscriptions module.
3
3
6
89
Upd4ting retweeted
Need to fix one row in production? In AntelopeJS DMS you don't open a database client for that. The Database module puts your app's database inside the back office: its health, its schemas, a diagram, the rows and a query console. Here's what each page does.
1
4
6
80
Long read, but the first section is enough to get the idea.
How our open-source back office went from a Postgres connection string to 12 pages of TypeScript in one agent run.
4
123
Upd4ting retweeted
How our open-source back office went from a Postgres connection string to 12 pages of TypeScript in one agent run.
5
5
1
11
295,411
Upd4ting retweeted
6 ans que j'avais ce projet en tête. Je l'ai enfin présenté en live : @TenkaiCloud Vos propres serveurs, le confort d'un PaaS, sans toucher à Docker. Cluster multi-provider, Postgres en haute dispo, backups chiffrés.... La présentation complète en live 👇 youtu.be/pWjFsBiBKqU
3
11
44
4,489
Looking for people to break our Cloud. The first wave of the beta opens soon, so sign up to get in. It's free for the whole beta, you get a direct line to the team on Discord, and we'll fix what you find.
Built your back office with AntelopeJS DMS? Next question: where does it run? AntelopeJS Cloud is in private beta, and everything is free for the whole beta: deploys, PostgreSQL and Redis, preview environments. Nothing is billed, whatever you run. The first wave of testers opens soon. Sign up now to be in it, then push your code or any Docker container, tell us what breaks, and we'll fix it with you. Also coming: a DMS module to deploy your back office to Cloud in one click. Sign up for the beta: cloud.antelopejs.com
1
4
71
Recorded with @romainlanz at the end of August, and the query console crashed right on cue. A lot has changed since, so treat it as the early version and check the docs for how it works now.
Back in late August, our co-founder Antony (@Upd4ting) joined @romainlanz for a live tour of AntelopeJS DMS. The replay is now up, in French with YouTube's English subtitles. The product has changed a lot since that live. To see where it is today, start with the site and the docs. Replay: youtube.com/watch?v=yyn8QDJX…
1
6
118
Upd4ting retweeted
Who can see revenue in your back office? In AntelopeJS DMS, roles come from your pages, down to each block and each action. Untick what Support shouldn't see, then check it with "View as Support". The server refuses it too, so hiding a block isn't the only protection.
5
5
71
Upd4ting retweeted
Le DMS que @Upd4ting nous a présenté lors de la HackerHouse est released ! 👇 La VOD arrive tout bientôt
Your ERP runs on Postgres. Your CRM on MongoDB. The shop grew on its own. Three good programs, and none of them talks to the others. Meet AntelopeJS DMS: connect the databases you already run, and get one back office on top. Open source.
2
11
766
If you had to pick one from this list, which would it be?
Here's the AntelopeJS DMS roadmap. Shipped: connect your PostgreSQL, MongoDB or RethinkDB database and your coding agent builds the pages. In progress: the AntelopeJS Cloud private beta, a spreadsheet-style grid, a full calendar, and an AI Operator you can ask about your data in plain words. Next: deploy to Cloud in one click, MySQL and MariaDB, more payment providers. What should we build first?
1
47
Upd4ting retweeted
This is Helio, a made-up solar installer. Everything you see is what AntelopeJS DMS ships, with no custom code: → a dashboard with KPIs, alerts and charts → a sales pipeline as a kanban board → customer tables with tabs, filters and a record panel → and much more It's live and read-only. Log in and click around: dms-demo.antelopejs.com
4
5
140
After years of building, refining, and using AntelopeJS in real-world production environments, it's incredibly exciting to finally see this project step into the public spotlight. 🦌🚀 Proud of what we've built, and even more excited about what's ahead. antelopejs.com
Your ERP runs on Postgres. Your CRM on MongoDB. The shop grew on its own. Three good programs, and none of them talks to the others. Meet AntelopeJS DMS: connect the databases you already run, and get one back office on top. Open source.
1
1
23
Upd4ting retweeted
Your ERP runs on Postgres. Your CRM on MongoDB. The shop grew on its own. Three good programs, and none of them talks to the others. Meet AntelopeJS DMS: connect the databases you already run, and get one back office on top. Open source.
1
23
6
31
3,470
Tenkai now gives each pull request its own preview, on your own Servers. Open a PR and Tenkai deploys it, then comments the URL on GitHub. Each push updates it, and merging deletes it. Experimental for now, turn it on in your Team settings. tenkai.cloud/whats-new/pull-…
3
1
4
588
Upd4ting retweeted
Cela fait un moment que je travaille sur streambrd.com, un outil qui permet d’automatiser facilement ton live en réagissant aux événements Twitch. Parmi vous, je recherche mes premiers early adopters pour le tester et me donner vos retours honnêtes. Je propose aussi en beta la création des overlays sur-mesure pilotés par Streambrd, donc si ça vous tente, répondez à ce tweet ou envoyez-moi un DM !
1
4
8
610
Tenkai now supports @infomaniak Public Cloud as a first-class citizen to create and manage your Servers, in Geneva. Connect an application credential, pick a region, Debian or Ubuntu, and Tenkai sets the Server up. Infomaniak bills you directly, in CHF. tenkai.cloud/whats-new/infom…
3
1
13
2,180
Tenkai is out of private beta 🎉 Turn a server you own (a VPS, a bare-metal box, a Raspberry Pi) into your own platform: push your code, get HTTPS, databases and rollbacks. Free for one server, no credit card. tenkai.cloud
3
7
390
Meet Hako 📦 The AI assistant built into Tenkai. Ask about your Projects, debug a failed Deployment, and approve every fix it proposes. Available on all plans. tenkai.cloud
2
1
9
1,995
Meet Tenkai. It turns a server you own into a deployment platform: a cloud VPS, a bare-metal box, or the Raspberry Pi on your shelf. Push your code, get HTTPS, databases, and rollbacks. The machine stays yours. Here is how it works 🧵
4
1
1
7
1,780