For the past 10 years, we have been running a development and design agency, completed more than 100 projects and most of them involved developing a mobile app or website with an API in the background.
While developing APIs we noticed that a lot of time is “wasted” on non-development-related tasks like: writing and maintaining documentation, providing support to other developers, debugging user reports, trying to recreate user steps and similar.
Because of this, we build Treblle, an API management and monitoring tool that helps you understand what’s going on with your APIs from development to post-production.
5 months since we got funded we are officially launching.
I think deepfakes will become a cat-and-mouse games. Deepfake text/images/videos will get more realistic, people will figure ways to "expose" fake deepfakes, and the wheel will keep turning.
Treblle allows you to test API requests with one click. Because Treblle knows what data was sent and what was returned it can replicate any call that the user has made and quickly allow you to re-run specific requests. Treblle also provides you with a way of running manual tests from our platform.
It also has an auto-generated documentation feature. Treblle can generate the required documentation for each endpoint just after 1 API call. It understands your JSON responses, can detect various authentication methods, group variable URLs in a single endpoint, support different documentation versions, and similar.
I'm currently working on a new tool called Launch Torch.
The idea is to ease the domain search of any company and get their activity on different launch platforms. We offer information like where and when they launched, how many upvotes, comments, and reviews they got. We would be grateful if you devote a few minutes to check our product and tell us if you find it useful in a comment.
Link your project in the comment section and I will give you feedback.
I’ve build a log management platform out of frustration at the lack of competitive pricing and stagnant feature sets of existing logs management companies.
Target Customer:
Developers, System administrators, Devops, CTO’s , or who ever needs a log management platform.
Wrble at the moment is being used by a number of early adopters and teams in our community. We have also been using Wrble internally for the past few months as well.
I would love to hear your comments, feedbacks and thoughts.
I'm gonna use your disasfaction of your log management tool for a little self-promotion. I'm working as part of the Wrble.com team its a fast logging platform that is priced way lower than hosting your open source stack. We are based on Lucene technology. I believe we provide the same service that existing players do for an 80% reduction in spending. Give it a shot let me know what you think.
Every time I'm starting a new service to run internally or reviewing something we have going, I find myself struggling to find the right instance type for the needs.
For instance, there are three families (r, x, z) that optimize RAM in various ways in various combinations and I always forget about the x and z variants.
So I put together this "cheat sheet" for us internally and thought I'd share it for anyone interested.
For the last few days, I’ve been scouring the web for “SaaS” founder interviews. The goal was to find insights on which acquisition channels worked for them on getting new users.