Syef here, one half of a two-person security startup. We built a thing that looks at a web app from the outside the way an attacker would, and the one rule we hold to is that it only calls a finding PROVEN when it can actually prove it. Everything else gets labelled refuted, inconclusive or not tested, because a list of maybes helps nobody. Right now we need real apps pointed at it more than we need anything else. So: drop a domain you own or are authorised to test, and I'll send you what we find. Including "nothing", if that's the honest answer. External only, nothing to install, no account, no call, and no follow-up pitch unless you ask for one. What I'd like back is where the report was useless to you. That's worth more to us than a thank you.
For the past year and a half I've been building Excalibase, an open-source platform as a service. One project gives you:
Databases: Postgres 15 17 or MongoDB-compatible DocumentDB, with backups and point-in-time restore
APIs: GraphQL and REST generated from your schema, with permissions per table and role, closed by default
Realtime, storage and edge functions (TypeScript on Deno)
App hosting: deploy any container next to your database, deploy from your CI
The newest part is an MCP server. Connect Claude Code, Cursor or Codex, give it one prompt, and the agent creates the tables and permissions, deploys the app and tests it. 2.5-minute demo: https://media.excalibase.io/demo...
I'm Darya, the solo founder of Lumeria Skyn which is live on the homepage today.
Six months ago I had never written a line of code. I work full time in finance. I have two small kids at home. I built Lumeria because I was exhausted by skincare advice that wasn't built for my skin. Dermatologists pushed retinoids. Influencers pushed whatever they were paid to push. Every app I tried wanted my data more than it wanted to help me.
So I built something different.
Lumeria asks six questions and builds a complete personalized morning and evening skincare routine for your exact skin type, conditions, and sensitivities. Gentle mode activates automatically for eczema, rosacea, and prescription skincare users. There's a barcode scanner that checks any product against your profile instantly. No account. No data collection. Everything stays on your phone.
When writing or optimizing articles for search engines, striking the right balance with term frequency is essential. Overusing target keywords can lead to search engine penalties, while underusing them might make it harder for algorithms to grasp the main topic.
I recently built NickMint, a free gamertag and username generator for gamers.
It helps you quickly generate gaming names by style and length, browse ready-made ideas, save favorites, and build a shortlist. It works well for names used on Xbox, Roblox, Fortnite, Minecraft, Discord, Steam, VALORANT, and more.
I wanted to make something simple, fast, and free without requiring an account just to generate a few names.
On 16 august i started banalo.business. Today we re at 2.7k total users and 1,100 signups. it s a b2b platform, so those signups are people who actually want to build something.
I ve only been in the startup world for 2 months, so even the small wins still get me excited. i check the numbers way more than i should lol.
I ll post a month by month update here so you can watch it grow with me. If you re building something right now and it feels slow, this is what the start looked like for me.
If you publish sports content regularly - match recaps, weekly digests, tournament coverage - the format you distribute it in may be worth a closer look.
Static PDFs have been the default for a long time. They are familiar and easy to produce. But there are a few practical limitations that tend to surface when you are publishing on a fast turnaround schedule and trying to reach an audience that reads mostly on mobile.
For years I've seen teams perform the same activity: A feature is implemented. Before anyone creates a maintainable automation suite, developers and testers spend time exploring the system. Sometimes manually. Sometimes using fuzzers, mutation tools, schema generators, protocol analyzers, API scanners, AI-assisted tools, or other forms of generated testing. The goal is not regression protection. The goal is discovery.
Hundreds of tests may be generated and executed. Many are never maintained. Some reveal defects. A few become future regression tests. Yet we usually classify this activity as either exploratory testing or test automation, even though it doesn't fully fit either category.
