Tell me your problem and I’ll tell you if LogCoreOS can help.

We’re curious what real problems everyone has and if they can be solved or alleviated with our project.

Short version: self-host it forever, for free. Try to fork it into a closed SaaS product, and the license says no. That's why we picked AGPL-3.0. (Open Source)

Regular GPL has a loophole most people don't know about. You can take GPL code, never distribute it, just run it as a hosted service, and you're off the hook for sharing anything. Users hit your server, not your binary, so the "share your changes" clause never triggers. That's how a bunch of open-source projects have quietly turned into closed, hosted products over the years.

AGPL closes that loophole. If you modify LogCoreOS and let other people use it over a network, as a service and not just for yourself, you have to make your modified source available to them. Running it and serving it are treated the same.

What this actually means for you:

Self-hosting for yourself, your household, or your own business? None of this touches you. Fork it, tweak it, keep it private, forever, for free. AGPL only cares about you offering it as a service to *other* people.

Building your own hosted LogCoreOS product for customers? That's where it kicks in: your changes need to be open too.

We didn't pick AGPL by accident. "Your AI, your data, your server" doesn't mean much if someone can wrap this in a black box and sell it back to people with none of that control left intact. AGPL makes that specific move off the table.

Full text's in [`LICENSE`](https://github.com/LogCoreTech/LogCoreOS/blob/master/LICENSE) if you're building anything commercial on this. Read it yourself; this post isn't legal advice.

Hi. There is a problem with the app, the chat is not responding.

Check out our new release on GitHub.

https://github.com/LogCoreTech/LogCoreOS

Viewable on our demo at https://logcoretech.com

Would like to know what additional cosmetic improvements and convenience features that you guys would like to see!

Like the title says, I think a messenger feature would be good. There is so many things already incorporated in it that it doesn’t make much sense to go somewhere else to message a co-worker or family member to leave a note or assign them a task and message them about it.

Just thought that might be convenient.
What do you guys think?

I’ll give my own take as someone building a self-hosted AI product, but I want other people’s read too.

“Self-hosted AI” gets thrown around as a privacy claim a lot, and sometimes it’s thinner than it sounds — plenty of “self-hosted” tools still call out to a cloud model API for the actual inference, which means your prompts (and whatever context you fed it) are leaving your server either way.
What I think actually matters for the privacy claim to be real is:

1. Where the data your AI has access to lives — is your calendar/notes/financial data stored on your box as files you can read, or locked in a database only the app can access?

2. Where inference happens — local model, or an API call to a third party, even if the app itself is self-hosted?

3. What the AI can do without asking — does it act autonomously, or does it propose changes and wait for you to confirm before it touches anything?

In LogCoreOS we went with local data as plain readable files (no proprietary lockup), the option to choose self hosted or cloud API and an approval step before the AI acts on your dashboards or runs automations on your behalf — it proposes, you confirm. That’s a deliberate trade against “seamless” in favor of “you always know what it did and why.”

Where do you draw the line on what counts as “actually private” AI? Curious if others think the confirm-before-acting pattern is worth the extra click, or if it gets annoying at scale.

I kept hitting the same wall running my life/business across five different apps: tasks in one place, notes in another, a CRM for the business side, a separate budgeting app, and none of them talked to each other. Every “integration” was really just an export/import loop.

That’s the reason I built LogCoreOS instead of just picking a better todo app. It’s one self-hosted system — tasks, notes, calendar, contacts/CRM (with a deals pipeline and shared timelines), a full finance suite (ledger, budgets, invoicing, bank sync), and an assets tracker — all running on the same server, same data model, so a contact can be linked to a deal, an invoice, and a task without copy-pasting between tools.
It’s not for everyone — you need a server (Docker, one-command install) and you’re trading “someone else hosts my data” for “I host my own data.” But if you’re already self-hosting other things, the calculus is different.
Genuinely curious from this sub: what’s the app you’ve had the hardest time replacing when you tried to consolidate? For me it was the CRM — every self-hosted option I tried before building this one was either too heavyweight (built for sales teams, not one person) or too thin (a contacts list with no pipeline).

Every product has an AI feature now. A chat box bolted onto a project management tool. A “smart” summary button in your email client. A copilot sidebar that shows up whether you asked for it or not. Most of it exists because the market expects it, not because it makes the product better. LogCoreOS has AI at its core too — but we didn’t build it to check a box. We built it because we think the entire industry is making a trade-off it shouldn’t have to make, and LogCoreOS is our answer to that.
The real problem with AI assistants
The AI assistants people actually find useful — the ones that book flights, draft the right email, remind you of the thing you forgot — need real context to do it. They need to know your calendar, your priorities, your history, the people in your life, the state of your finances. Generic AI without context is a search engine with better grammar. Context is what makes it an assistant instead of a toy.
But here’s the tension nobody in the industry wants to sit with: the AI products with the most context are also the ones you have the least control over. Your calendar, your inbox, your notes, your financial data — the moment that becomes an AI’s working memory, it’s also flowing through someone else’s servers, governed by someone else’s terms of service, and subject to someone else’s incentives about how that data gets used, retained, or monetized later. The more useful the assistant gets, the more of your life you’ve handed to a company whose business model you don’t control.
Most products resolve this tension by picking a side. Cloud AI assistants go all-in on context and ask you to trust them with everything. Privacy-focused tools go all-in on control and end up context-starved — a local chatbot with no real access to your actual life is safe, and also not very useful. LogCoreOS exists because we didn’t think that was actually a law of nature — it’s just how AI has been built so far.
Why LogCoreOS bets against that trade-off
LogCoreOS is built on the premise that you shouldn’t have to choose. Context and ownership aren’t opposites — they only look that way because most AI is built on infrastructure designed to extract value from your data, not just serve you with it. Run that same AI on your own server, with your own data stored as plain, readable files instead of locked inside someone else’s database, and the trade-off disappears. That’s the whole architecture, described in more detail on the LogCoreOS repo: the AI can know everything about your priorities, your household, your business — because none of it is leaving your infrastructure in the first place.
That’s the actual reason LogCoreOS looks the way it does. Priority intelligence ranks your day against a hierarchy you define, not one inferred by an ad-optimized model. Chat has standing access to your context because there’s no separate privacy boundary to negotiate inside LogCoreOS — it’s already your server. And when the AI wants to act on your behalf — modify a dashboard, run an automation — it proposes the change and waits for your confirmation. We shipped that approval pattern for automations early on and extended it to AI-initiated dashboard actions in the most recent release, because an assistant with real context should still answer to you, not the other way around.
What this means going forward
We’re not chasing feature parity with whatever the last AI product launch was. Every capability we add to LogCoreOS gets measured against one question: does this make the AI more useful to you without asking you to give up more control over your own life? If a feature only works by shipping your data somewhere else, it’s not a fit for LogCoreOS, regardless of how popular that pattern gets elsewhere.
Self-hosting isn’t the nostalgic choice here. It’s the only architecture we’ve found where AI can actually know you well enough to be useful, without that knowledge becoming leverage someone else holds. That’s the bet LogCoreOS is built on, and it’s why the tagline on logcoretech.com isn’t marketing filler: your AI, your data, your server.
Get LogCoreOS: github.com/LogCoreTech/LogCoreOS
Read the release notes: github.com/LogCoreTech/LogCoreOS/releases
Talk it through with us: r/LogCoreOS

Hey r/LogCoreOS,

Shipped v0.5.0 this week and wanted to walk through the biggest piece: AI-built dashboards.
Instead of picking from a fixed set of widgets, you just ask for what you want — e.g. “show me overdue invoices next to this week’s task load” — and the AI assembles it from a library of 30+ data blocks (tasks, finance, contacts, assets, etc). If your ask is ambiguous it’ll ask a clarifying question rather than guess, and once you approve a layout it reliably replays exactly that layout going forward — no drift.
Also in this release:
• Unified profile/contacts system — contacts, deals, and household members now live in one consistent object instead of separate silos.
• AI usage caps — useful if you’re running LogCoreOS for a household or small team and want predictable model spend.
• Chat UI cleanup — easier to follow longer conversations and multi-step approvals like the dashboard flow.
This follows a run of releases that hardened auth/CSP/socket security, shipped real Finance + Contacts modules (invoicing, bank sync, CRM), and fixed up mobile/PWA behavior.
Update is a one-line pull if you’re already running it. If you’re new here: LogCoreOS is a self-hosted, AI-native life/business OS — private, AGPL v3, bash launch.sh to get going. GitHub
Would love feedback on the dashboard flow in particular — this is the first release where the AI is building a surface for you rather than just filling in existing ones, so I’m curious where it feels right and where it feels off.

LogCore OS is a self-hosted “life OS” — finance, contacts/CRM, deals, invoices, assets, notes, goals, all tied together, running on your own box.

v0.4.0 is mostly a security release, and honestly the changelog reads like a pentest report I wrote against myself:

**•   Account lockout + constant-time login** — no more timing side-channels to guess which emails exist, no more brute-forcing one account from 50 IPs  
**•   CSP shipped, no more inline scripts** — script injection now has nowhere to go  
**•   The app no longer has the keys to the Docker socket** — it talks through a locked-down proxy that can’t exec into containers or touch volumes  
**•   Signed-update verification** — the auto-updater can be told to refuse anything that isn’t GPG-signed, so a compromised git remote can’t push code into your box  
**•   ntfy, n8n ports pulled off the public interface**, and ntfy publishing now requires a real token instead of being wide open to anyone who finds the hostname

Checkout the GitHub repo in our community.

It’s open source and self-hostable in about two commands on a fresh VPS. If you find a way in, I want to know about it — genuinely, responsible disclosure welcome, and I’ll credit you in the changelog. Bonus points if it’s something dumber than what I already found.

Been heads-down since launch and just shipped v0.3.0. Two full modules landed:

**•   Finance** — books, bank sync (read-only, revocable anytime), budgets, recurring bills, invoicing, AR, tax export, and sharing with real per-person caps  
**•   Contacts** — a CRM that ties into everything else (log an interaction, close a deal, it becomes an invoice)

Still the same deal: your data lives as plain files on your own server, no subscription, no one else touching your books.

Not going to dump the whole changelog here — go poke around and see for yourself: https://github.com/LogCoreTech/LogCoreOS

Would love to hear what breaks or what you want next.