Your are here

Your idea of combining MPTCP with Tailscale for a P2P mesh VPN with link bonding falls into a category we've labeled 'Minimal Signal.' With only one similar product identified, confidence in this assessment is low, indicating a potentially niche or unproven market. While Webmesh, a Tailscale alternative, shows some traction, it doesn't directly validate the specific combination of MPTCP and link bonding. The low engagement (average of 3 comments on similar products) suggests limited discussion or validation around such solutions. You are at the very early stage, so it's crucial to avoid premature investment before validating real demand. The path forward involves actively proving the existence of a genuine need before committing substantial resources.

Recommendations

1. Begin by actively engaging in online communities where your target users (e.g., network engineers, remote workers) gather. Clearly articulate the benefits of MPTCP and link bonding within a Tailscale-like mesh VPN context, and gauge their explicit interest and potential use cases. Quantify this interest by tracking engagement metrics like comments, shares, and positive reactions to your posts.
2. Identify 2-3 potential users who face connectivity challenges that your solution directly addresses (e.g., unreliable internet, need for high bandwidth). Offer to solve their problems manually by setting up a prototype or even a workaround using existing tools. Document the time savings, performance improvements, and overall satisfaction of these users to gather concrete evidence of value.
3. Create a concise explainer video that showcases the core functionality and benefits of your MPTCP-Tailscale solution. Focus on real-world scenarios and highlight the unique value proposition. Monitor video completion rates and feedback to assess whether the concept resonates with your target audience.
4. Gauge commitment by asking for a small, non-binding deposit to join a waiting list for early access to your product. This helps filter out casual interest from genuine demand and provides a tangible measure of market validation. Make sure that you communicate with them that you are validating the idea and their deposit is fully refundable. This builds trust.
5. Set a clear deadline of 3 weeks to find at least 5 genuinely interested individuals willing to provide a deposit. If you cannot reach this threshold, critically re-evaluate your value proposition, target audience, or overall market viability. Consider pivoting to a different approach or addressing a different problem within the same domain.
6. Since Webmesh highlights the importance of open-source alternatives, consider the open-source strategy to build trust and community around your project early on. Identify the core components that can be open-sourced without compromising your competitive advantage.
7. Given that IPv6 forwarding was mentioned as a positive feature in a similar project, ensure that your solution has robust IPv6 support. Emphasize this capability in your marketing materials, as it can be a key differentiator for your target audience.
8. Given the low number of similar products, prioritize validating the core assumption: Does combining MPTCP and Tailscale solve a significant pain point for a specific group of users? Focus your initial efforts on answering this question before building out additional features.

Questions

1. Considering the complexities of MPTCP and network configuration, what specific user segment would find the benefits of link bonding most valuable, and how can you reach them effectively?
2. Given that Webmesh focuses on WireGuard, what are the key technical trade-offs between using WireGuard versus Tailscale's underlying technology (Noise protocol) for your specific use case, and how do these trade-offs impact user experience and security?
3. Assuming that you will implement a P2P mesh VPN, what strategies will you employ to address the NAT traversal issues and how will that affect the end-user experience and the complexity of setting up the VPN?