Hey everyone

I m Mohammad, and I built natbox.io: small Linux servers starting at $1/month.

A lot of what we run doesn t need a full VPS with its own IPv4. A Discord bot, a personal WireGuard VPN, an Uptime Kuma monitor, a test box or a small API will all run fine on something much smaller and cheaper. So I built that.

I've been building GhostCall, a small project built around a simple idea: you shouldn't always have to share your personal phone number just to talk to someone.

Think about a few everyday situations:

• You're talking to a potential client for the first time.

• You're buying something from a stranger online.

• You meet someone through a social platform and want to have a quick call.

• You need to speak to someone once but don't necessarily want to exchange permanent contact details.

Usually, you end up sharing your number, asking the other person to install an app, or settling for text messages.

Hey PH community!
We re preparing to launch Riftur, an AI tool within the gap analysis space that helps you compare two documents and instantly see what s missing, incomplete, or inconsistent. It s designed for anyone who works with requirements vs. deliverables proposals, audits, compliance matrices, education materials, internal SOPs, etc.

We ll be going live on Product Hunt soon, but before we do, we d love to gather some early feedback from this group:

• Does the problem/solution resonate with you?

• Which use cases feel strongest?

• What would make the product more appealing ahead of launch?

Really appreciate any thoughts. Excited (and slightly nervous) to share Riftur with everyone soon

I run Shelf by JC, where people who build apps with AI get a "shelf": one page that shows what you ve made, so others can find it and try it.

I m looking for apps to feature to my Facebook community (26,500+ women entrepreneurs) and my email list of about 3,000.

A small website-launch task can turn into three separate jobs: build the footer, make its links measurable, and check what is already on the live site.
I build 1Footer and added three free tools for that workflow:
1. Footer generator: choose from the current app templates, adjust the style and copy static HTML/CSS.
https://1footer.com/tools/footer...
2. UTM link builder: tag project links before putting them in the footer. Your analytics still needs to collect and reconcile the visits and conversions.
https://1footer.com/tools/utm-li...
3. Footer checker: inspect the structure of an existing website footer.
https://1footer.com/tools/footer...
No account is needed to use the tools. Here is the real-screen generator walkthrough:
https://1footer.com/tools?utm_so...
The generator uses the core app's template catalog and renderer; copied HTML is a static snapshot. Managing shared footer updates across multiple sites is the separate app workflow.
For founders managing several sites, is getting a first footer done the hard part, or keeping its links current after launch?

Quick context: I built Shayari NHE-01, an AI companion with memory and personality. Early on I obsessed over making her replies instant. Every millisecond shaved felt like progress.

Then I watched people actually chat with her.

I've been building a tool (tool) that ingests my bank and credit card statements and builds a dashboard. It's still pretty new, but I've got a small number of users who are giving me some feedback.

I'd love to hear why you think this product is useless, confusing, lame, hard to understand, has a very weird landing page, etc.
I'm still trying to figure out which "direction" to take this project and looking to be directed by a good roast.

I'm part of the XWiki team, and we've recently released an open-source MCP server that lets AI agents interact directly with content stored in XWiki, our knowledge management and collaboration platform.

The idea came from a challenge we're seeing more often: organizations have years of documentation, procedures, and structured knowledge in their wikis, and they want to make that information accessible to AI agents without moving it to another platform.

With the MCP server, agents like Claude Code, Codex, and OpenCode can search and read wiki pages, access attachments and page history, query structured data, and create or edit content.

One design decision we'd particularly like feedback on is how we handle permissions and write access. The MCP server uses XWiki's existing permission system, so authenticated agents act with the rights of the user they're connected as. Write operations are disabled by default and need to be explicitly enabled by an administrator.

Hi, everyone!
It has been two - three months that we work on the idea of the app - planing trips together. The idea is to save all your favorite reels, youtube, tiktok places that you saw on social media to a board, make a plan, buy ticket, set budget and plan together with friends to make it come true. It is Free, by the way.

Sound interesting ? Try here : lezen.io

We are still waiting to get approved from IOS apple store T.T so please try it on Test Flight.

Happy to take any feedback!

I m a packaging designer working with a print shop, and the same thing keeps happening: the mockup wins the client, then the file has to be rebuilt on a real dieline before it can go to press. Wrong bleed, RGB, foil on the wrong layer

I ended up building a tool for myself (Drint) where you design on the dieline and the 3D is that die folded, so the mockup and the print file are the same thing.

Curious how others handle this:

• Do you design on the die from the start, or mockup first?

• What breaks most often when your file reaches the printer?