Why Texas 67 Systems Runs on Docker and Open Source

When most people think about business technology, they picture subscriptions, vendor lock-in, and software they never really get to control. I wanted something different for Texas 67 Systems. I wanted tools that were practical, flexible, and understandable enough to maintain over time. That is a big reason I leaned into Docker and open source software.

If those terms sound technical, that is fine. They matter less as buzzwords and more as working parts of a system.

What Docker means in plain language

Docker is a way to package software so it runs consistently across environments. Docker’s own overview explains containers as a way to separate applications from the underlying infrastructure so teams can ship and manage software more reliably.[1] In plain language, that means I do not have to rebuild a full server every time I want to test, move, or update a service. I can bring up the right container and work from a cleaner starting point.

That consistency matters more than people think. A lot of technical headaches come from “it works on one machine but not the other.” Containers do not solve every problem, but they do remove a lot of avoidable differences.

What open source means

Open source software is software released under licenses that let people inspect, improve, and share the code.[2] For a business, that usually means more visibility, more flexibility, and a better chance of keeping control of your own systems and data.

That does not mean open source is automatically easier. It still needs hosting, updates, backups, support, and good judgment. What it does offer is room to build a stack around your actual needs instead of around whatever a single vendor decides to sell next.

Why this matters at Texas 67 Systems

This is the reason I built the environment the way I did. Docker helps keep services organized and easier to move, test, and maintain. Open source tools make it possible to build a stack that is owned by the business instead of rented blindly from someone else’s cloud by default.

Some of these tools help with operations. Some help with communication, websites, documents, password management, scheduling, or support. The point is not to run a long list of software for bragging rights. The point is to have tools that solve real problems.

Here are the main services I am running, or planning to run, for Texas 67 Systems.

• Authentik for identity and access
• Gitea for code hosting and development work
• Invoice Ninja for invoicing and billing
• ERPNext for business management
• Snipe-IT for inventory and asset tracking
• Documenso for signed documents
• OpenArchiver for archived records
• Paperless-ngx for searchable document management
• RustDesk and MeshCentral for remote access and support
• Rybbit Analytics for analytics
• Synapse for team chat and communication
• UniFi Network Application for network management
• WordPress and MainWP for websites and site management
• Vaultwarden for password management
• cloudflared for secure publishing and connectivity
• Stirling PDF for PDF work
• Node-RED for automation
• Nextcloud for calendar integration, chat, and meetings
• Joplin for notes and documentation
• Posterr for media room and theater display ideas
• Easy!Appointments as a planned scheduling tool

Authentik helps manage sign-in and access across services. Gitea keeps code, changes, and project history in one place.[3] Invoice Ninja and ERPNext cover the business side of the house. Snipe-IT, Documenso, OpenArchiver, and Paperless-ngx help keep records and documents from turning into a mess.[4][5]

RustDesk and MeshCentral make remote support more practical. Rybbit Analytics, Synapse, the UniFi Network Application, WordPress, MainWP, and Vaultwarden each handle a different part of day-to-day operations. cloudflared helps with secure publishing, Stirling PDF handles document work, and Node-RED is useful when repeatable tasks should stop being manual.[6]

Nextcloud and Joplin matter for a different reason. They help with organization. Nextcloud covers much more than file storage and can also support collaboration, calendars, and meetings.[7] Joplin is where notes, ideas, and operating details can stay accessible instead of drifting across random files and devices.[8]

Easy!Appointments is still on the list rather than fully in place, but it is the kind of tool that could make scheduling cleaner later.[9] That is how I think about the whole stack in general. Every service should earn its place.

What comes next

The goal is not to run a lot of software for the sake of it. The goal is to build a stack with a reason behind it. Every service should solve a problem, save time, improve control, reduce confusion, or make support more reliable.

This first post is the big picture. The next posts in the series can slow down and look at one main service at a time, what it does, why it matters, and what it is like to use in a real business environment.

This is not just a list of containers. It is the start of a business system that is practical, understandable, and actually owned by the business using it.

Sources

• Docker Docs: Docker overview
• Open Source Initiative: About
• Gitea documentation
• ERPNext documentation
• Paperless-ngx documentation
• Node-RED: About
• Nextcloud
• Joplin help and overview
• Easy!Appointments

Next in the series: Why Authentik Matters for Texas 67 Systems explains how sign-ins, single sign-on, and access control fit into the bigger picture.

Frequently asked questions

Why use Docker in a small business stack?

Docker helps package services consistently, which makes deployments, updates, and rebuilds easier to document and repeat.

What is the practical benefit of open source here?

More visibility, more flexibility, and less dependence on a single vendor. That does not remove responsibility, but it can improve control and long-term adaptability.

Does open source always mean lower cost?

No. The real value is not just cost. It is whether the tools are maintainable, appropriate, and aligned with how the business actually operates.