We’re actually working on our own API security feature and OWASP Top 10 is wheree we started. The peoblem is - it’s almost impossible to automate some of those checks without human input. So we’re working to make it as smooth as possible
I can tell you the origin story of it maybe you like it more. I was sitting on my balcony with my cofounder and we were thinking of names that had .com free and no registred TM. As you might imagine the list was pretty short.We had names like apilogger.com, apicapture.com, restlerr.com, apigga.com
We thought that it would be cool to have something with treble(high pitch sound opposite to bass) but the domain was taken. I also liked it because it was in the same keystroke as Trelloand i associate Trello with productivity. So we added another L and took home the win :)
Hi everyone, i’m a full-stack dev with more than 10 years of experience. I mostly work with PHP/MYSQL/Laravel and HTML/CSS/JS. I also absolutely love web performance and speed optimization. In my career i spent a lof of time consulting on performance optimizations and saw all the good but also all the bad stuff people do
I wrote an article about some of the things i most often saw people doing wrong on all three sides: front-end, back-end, infrastructure. I tried to focus on the things you can do in a day and bring your Lighthouse, Pingdom or GTMetrix scores up.
Hope it helps and let me know what you think about the article
Hello everyone hope a lot of Laravel fans are here just like me : ) Let me know if you have questions about Laravel or Vapor. Also if you can give some feedback in terms of the quality of the article i would love that. Given that it's among the first ones i wrote. Thank you
The biggest idea being Treblle is the ability for EVERYONE involved to see requests in real time in a format that is understandable to the average person in tech, not just a back-end developer. Most mobile developers can't read server logs nor they have access to servers that have them. Because we have access to every request we can compute things that you won't find it the logs: like request/endpoint documentation, location data, device information, app version, os version, server environment. More importantly you can literary search any request made to your API. So you can say something like: "Find all requests coming in from Las Vegas, to the Auth endpoint, from iOS withing the last 3 days". It can be even more granular.
Also we actually generate and update your API documentation continuously including an OpenAPI Spec version.
Thank you for your comments especially on the website we are working on it and on the redesign. We just got our seed round and we are looking to make things super polished so stay tuned.
I would love to show you around Treblle if you want ping me at [email protected]
Hi there i’m the founder of Treblle and also the guy who developed it all;) So the website itself is built using HTML/CSS/JS on the front-end and PHP/MYSQL/LARAVEL on the back-end. We didn’t use any fancy frameworks for the front-end because we managed to do what we want just with CSS. Plus it really helps with performance and loading times if you cut down on JS frameworks. To make sure it scales we use a lot of AWS services on top of Laravel Vapor. If you have any in depth questions about the tech stack let me know.
Thank you for your comments! I am glad you would consider it. We originally had a 30 dollar package but thought that it might be to many options. We will adjust that based on your feedback :)
When you say "replicating and storing the logs myself". It's not just about the RAW logs - it about who gets to see them and how. Because Treblle allows you to search those logs and say something like "Give me all requests for endpoint X withing a Y time frame that were made from New York, US". So yeah you could be logging thing to CloudWatch but it will just be logs who are not readable to the average person in my opinion. When you share a request from Treblle anybody can understand it, it's full of information that the original log doesn't have like the API version, device information, server information, location data and much more.
Personally as a developer i also hate when you have to buy the biggest package just so you can get the feature you want. I find it sleazy. This way you literary pay for the requests and the retention period you need.