We built a SaaS product, wrote articles, made videos, but still no luck getting it off the ground

I got the idea of the service without even visiting the website :-) My 2 cents:

• there is definitely a problem that you need to keep your configuration at the 3rd-party (you). That would be a blocker for me and any company I worked with the in the past. If you cannot store secrets at the 3rd-party, you need two different solutions. This would only work with the high level of trust or for not very important projects or projects by non-developers. For serious projects most developers would prefer something like Hashicorp's Vault or the provider's solutions like AWS Parameter Store.
• the security and high availability is very important for a configuration service and requires a lot of engineering (like encryption). The pricing indicates that these aspects probably are not taken care of.

Also, going to the Internet to fetch the configs for your app is not efficient. I would prefer to host the service in my own network. And here I would suggest to go the Hashicorp's way. First, build an open source product which solves the config management well and gets adopted by developers because it's better/different than alternatives and then sell premium features to enterprises. Otherwise, I have a feeling that it would be hard to find a niche for the product (but might be still possible, you never know :-) ).

If you're expecting to get distribution on Medium you need to be publishing in publications... either that or writing articles that catch the attention of the Medium curation team. Articles like that target bigger dreams and desires... eg: succeeding as an entrepreneur, getting your first job as a developer etc...

It's not hard to get your articles into publications. They need good content so write another article and see if you can get it into a publication. You'll definitely get more results than just posting on your personal account.

Very cool concept!

Content marketing and defining your product market fit can be tricky, but not impossible - it just requires experimentation and hitting the right messaging.

Off the bat it looks like you serve two use cases: updating websites and updating web apps remotely and without code (at least after the initial setup is done) is that a correct distilling of your product?

Ultimately you want to target the buyer with your messaging, and consider them in the content you create as well as how you structure your landing pages. Do you have active users now? If so, who's the primary user/set of users and who's the buyer? What is the primary benefit they are seeing? I can see many use cases but really you want to focus on a set of use cases to really sell to and get usage and feedback around.

Once you have a really strong concept of the need you are meeting and selling to, you'll be able to start creating content that converts.

Your articles on Medium span quite a few topics and don't really mesh very well, for example a user might be interested in code-free updates but that specific user is not likely to be the same one who will know what a cron job is. Knowing the use case you meet, and the buyer helps you then determine the types of things they need help with and search terms they'd use (which is how you can start picking some really good and high-converting blog topics to start building traction). Your articles should be about topics your ideal customer cares about, not necessarily always product focused/advertisements for the product.

I'd also recommend longer articles, longform content (10min reads, around 1200 words) performs really well on Medium, but feel free to experiment (maybe shorter works better after you've had a run at it?)

I understand the idea and was just thinking that a product like this should exist...

What we have done for managing configuration is basically store the settings (credentials and site-specific) as a file on an S3 bucket and make sure all webapps read it when they (re-)start. Works good enough. None-the-less there are still some gotcha.

We do have a LDAP directory for user credentials, so maybe we should leverage it also for central configuration management? Maybe Okta would work as a central configuration repository? Onelogin? Or maybe just go with Ansible Tower? That is my thinking when landing on remoteconfigs.com...

Based on that, it looks like the homepage doesn't want to decide on the target customer and the problem that remoteconfigs solves for her. The current homepage looks great for a company in growth-stage making $10M ARR, but it is not focused enough as a company looking for product/market fit.

A missing section about overcoming objections might also be welcome:
1/ There is also no descriptions of the bootstrapping problem. How does the remoteconfigs.com API key makes it into my webapp? If I have to solve the bootstrapping problem myself, then why couldn't I use the same solution for other settings?
2/ You expect me to store credentials and/or other sensitive settings in a 3rd party product. Do I get to host it on my own servers? Is RemoteConfigs SOC2 / HIPAA / PCI compliant?

Do you have any users? The first thing you have to do is validate the problem and the solution. You'll have to reach out to people directly for this. Contact your friends who might have the problem you're trying to solve.