Port514 – An Introduction

For a long time I’ve been wanting to make a SaaS product. Over the years this started as a complex product that realistically was too much for me as one solo dev to build. Heck, I’ve even blogged about it on this very website. Today is the first step in a very different methodology. However, Port514 is different.

Over the coming months and years I’ll be producing multiple small hyper-focused SaaS tools under my company quickfire platform limited. They will all run as separate products from this one unifying business (as this makes my life easier just having one business to do paperwork etc for).

The first is Port514. A fully cloud-based logging solution for networking hardware. The name comes from the fact that Syslog – the first supported protocol – runs on port 514, for the server portion at least.

For the past few weeks I have been building the foundation for the product and I’m excited to finally launch something. Initially it will be simple, and will be stripped down, but it will progress over time. One thing that will never change though is the focus of the product. I won’t be building services that start out simple and just become a bloated mess over time (hello, Google Chrome).

The focus will remain forever. Every feature, every text box, every button will be carefully planned and will only be there if absolutely necessary. Only things that add real value will be there.

So, what is Port514 then?

From the outset you will be able to set your network devices or servers to send their syslog messages to our server ready for processing. All of this is fully cloud-native and will scale as demand requires (either up and down).

This focus and attention to building something to leverage the cloud as much as possible means that no penny is wasted. Instead, all savings can be passed on to our members.

When a syslog message is sent, it is parsed by a proxy service (that runs on nodejs) and then is sent upstream to the platform which runs on Hetzner Cloud (managed through Laravel Forge). The entire webapp and backend API built upon Jetstream and sits within Hetzner Cloud along with the database, on separate servers of course.

So, that was a quick vomit of information. Below is the full tech stack behind Port514 nicely laid out, covering all services that will be used.

  • Hetzner Cloud for database, syslog ingest server and database servers
  • ConvertKit for mailing lists / email marketing
  • Stripe for payments
  • Xero for accounting
  • Transferwise for international banking
  • BunnyCDN for CDN (affiliate link of course)

So where do we go from here?

As this develops in to the MVP over the next couple of months, ahead of the beta launch later this year / early next year, I’ll be (hopefully… maybe) blogging here more regularly about the project. The posts will probably be pretty technical in nature as I discuss how various aspects are built.

I look forward to bringing this to the world, and finally launching a SaaS product.

If you’re interested, head over to the Port514 website now and join the mailing list to be updated on progress. Best of all, you’ll be the first to know on beta launch day and will get a nice discount too.

One thought on “Port514 – An Introduction”

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.