FlatClaw: Open Source Private Cloud AI Coworker

Flatclaw is the same product shape on private infrastructure that you can actually run without breaking regulatory compliance. We’re going to hear about that this year when the industry catches up with the realization that everybody’s been shipping so much of their information to these frontier models because it gives them such an advantage.

And to take away that ability is to take away that advantage. Well, this is that advantage on private infrastructure at frontier capability.

Flatclaw is a complete private co-working studio and suite. What you see here is the admin view. I’m logged in as an admin of Flatclaw, but also as Skyler, I have admin privileges within the ecosystem.

These are my custom service connections.

Skyler is connected to Jira as Skyler at Flatclaw connected to cPanel as sort of a root account that can do almost anything like upload or delete files, modify files, read backups, create backups, modify DNS, etc.

This is a highly privileged MCP connection that can do anything that only this admin user has access to.

Each user also has access to their CalDAV. So you can consider that just like Gmail with an email box, a calendar, and a contact list that’s all part of one account.

So let’s demonstrate a little bit how role-based co-working can work in a private institution or organization.

Right now this is connected to the flatclaw.org services.

This is a file on cPanel. So this is an index file, a PHP file that generates this demo. This is just a demo of customer data. It’s just demo data.

This isn’t real data, but there are some notes in this file that were left from a developer that explains how to get this to phase 2, how to sort of upgrade it into the look and feel of phase 2.

So let’s do this all through Flatclaw.

Now acting as Skyler I’m going to say let’s copy the index file from the public HTML demo on cPanel then make a Jira ticket which describes looking at the notes in the file in order to make the phase 2 update and let’s assign that to Hemature.

Now we can see the Jira ticket was created for Hemature.

So now acting as Hemature, let’s get the attachment from the Jira ticket. Let’s look at the index file and look at the comments in it and let’s make those phase 2 updates.

Let’s do that. And then let’s attach that back to the Jira ticket.

Now acting as Skyler, I’ll look for the attachment that he should just added with the updates to that file on the Jira ticket.

Now the cPanel has actually updated that file. So we’ve created a Jira ticket. We’ve done the work on the Jira ticket and we’ve uploaded the file to the live production server of flatclaw.org.

So if we switch over here, we should be able to go to index2.php and we can see that phase 2 has been implemented all by the private LLM.

Let’s switch back over and just let Flatclaw know to update that Jira ticket as done.

And that’s it. We’ve created a Jira ticket and completed a Jira ticket across multiple users and updated the live production server.

And this was all done on a completely private co-working stack on infrastructure that you own.

The reason why it’s called Flatclaw is the claw comes from OpenClaw which is now one of the most highly maintained open-source projects. And you could consider it the Linux of LLM administration orchestration and a layer that can do role-based access control across region use case and team and department.

And the flat is because the price doesn’t change. You don’t have a relationship that is based on tokens. You have a relationship that you can understand. As your situation grows, there is a number of GPUs that you will be using that is at a flat rate that can be predetermined.

Meet with Kirk Tech Solutions to see how Flatclaw will help your business.Hi, my name is Skyler Truax. I’ve been in tech for about 20 years and focused on AI for the last three. I developed Flatclaw as an accelerator.

Role-based access to agents on private infrastructure is something that is more attainable. Co-pilot was one thing, but the industry changed when Claude Co-work came out early 2026. And every Frontier lab is rushing to ship the same product shape.

Flatclaw is the same product shape on private infrastructure that you can actually run without breaking regulatory compliance. We’re going to hear about that this year when the industry catches up with the realization that everybody’s been shipping so much of their information to these frontier models because it gives them such an advantage.

And to take away that ability is to take away that advantage. Well, this is that advantage on private infrastructure at frontier capability.

Flatclaw is a complete private co-working studio and suite. What you see here is the admin view. I’m logged in as an admin of Flatclaw, but also as Skyler, I have admin privileges within the ecosystem.

These are my custom service connections.

Skyler is connected to Jira as Skyler at Flatclaw connected to cPanel as sort of a root account that can do almost anything like upload or delete files, modify files, read backups, create backups, modify DNS, etc.

This is a highly privileged MCP connection that can do anything that only this admin user has access to.

Each user also has access to their CalDAV. So you can consider that just like Gmail with an email box, a calendar, and a contact list that’s all part of one account.

So let’s demonstrate a little bit how role-based co-working can work in a private institution or organization.

Right now this is connected to the flatclaw.org services.

This is a file on cPanel. So this is an index file, a PHP file that generates this demo. This is just a demo of customer data. It’s just demo data.

This isn’t real data, but there are some notes in this file that were left from a developer that explains how to get this to phase 2, how to sort of upgrade it into the look and feel of phase 2.

So let’s do this all through Flatclaw.

Now acting as Skyler I’m going to say let’s copy the index file from the public HTML demo on cPanel then make a Jira ticket which describes looking at the notes in the file in order to make the phase 2 update and let’s assign that to Hemature.

Now we can see the Jira ticket was created for Hemature.

So now acting as Hemature, let’s get the attachment from the Jira ticket. Let’s look at the index file and look at the comments in it and let’s make those phase 2 updates.

Let’s do that. And then let’s attach that back to the Jira ticket.

Now acting as Skyler, I’ll look for the attachment that he should just added with the updates to that file on the Jira ticket.

Now the cPanel has actually updated that file. So we’ve created a Jira ticket. We’ve done the work on the Jira ticket and we’ve uploaded the file to the live production server of flatclaw.org.

So if we switch over here, we should be able to go to index2.php and we can see that phase 2 has been implemented all by the private LLM.

Let’s switch back over and just let Flatclaw know to update that Jira ticket as done.

And that’s it. We’ve created a Jira ticket and completed a Jira ticket across multiple users and updated the live production server.

And this was all done on a completely private co-working stack on infrastructure that you own.

The reason why it’s called Flatclaw is the claw comes from OpenClaw which is now one of the most highly maintained open-source projects. And you could consider it the Linux of LLM administration orchestration and a layer that can do role-based access control across region use case and team and department.

And the flat is because the price doesn’t change. You don’t have a relationship that is based on tokens. You have a relationship that you can understand. As your situation grows, there is a number of GPUs that you will be using that is at a flat rate that can be predetermined.

Meet with Kirk Tech Solutions to see how Flatclaw will help your business.