5
10 Comments

Just released the source code behind Asknes πŸ§‘β€πŸ’»

I've been running Asknes (an AI study assistant β€” multi-LLM chat with document Q&A, source citations, flashcards, quizzes, and spaced repetition) solo for a while now, and I just packaged the entire codebase as a sellable SaaS boilerplate for other builders.

What's inside:

  • Multi-LLM setup (Groq, Gemini, Claude) with automatic failover

  • RAG-based chat with real source citations, not hallucinated answers

  • OCR fallback for scanned/image-based PDFs

  • Supabase auth + database, Stripe billing wired in

  • PWA support out of the box

It's the exact production codebase behind the live app at asknes.com, cleaned up and documented for reuse.

Grabbed it here if you want to skip months of setup and start from a working SaaS: https://tudora5.gumroad.com/l/asknes?wanted=true

Happy to answer any questions about the stack or the build.

posted toAvatar for product Asknes
Asknes
  1. 1

    Super solid build! Tested it with a few complex PDFs and the OCR fallback + LLM responses worked flawlessly. You can tell a lot of thought went into the underlying architecture. Really impressive SaaS product

    1. 1

      Thanks a lot for the support and feedback! Really appreciate you taking the time to test it out. Glad to hear the workflow and PDF processing worked smoothly for you

  2. 1

    The fact that this is the production code behind a live app is probably the strongest selling point.

    Curious whether buyers are mainly paying to skip the initial implementation work, or because starting from a codebase you’ve already validated removes the risk of stitching all those pieces together themselves.

    1. 1
      Honestly, a bit of both β€” but I'd say the bigger value is the second one. Skipping the initial scaffolding saves maybe a week or two, but the real risk buyers avoid is exactly what you said: stitching together multi-LLM failover, RAG with citations, auth, billing, and OCR fallback into something that actually works together reliably in production. I hit a lot of edge cases building this that aren't obvious until you're live with real users β€” this codebase already survived that.
      1. 1
        That makes sense. The production validation sounds like the more meaningful part of the asset.
        1. 1

          Spot on. Thanks for dropping by and sharing your thoughts, Aryan! Let me know if you ever decide to take a look under the hood

          1. 1

            That’s fair. I’ll keep it in mind if I decide to look under the hood.

  3. 0

    I just bought this today and I really enjoy it. It helped me with managing my time and my tasks a lot better. Even if I haven t used this for a long time I can tell that it will be a huge help for me.

    1. 1

      Thank you for buying and taking the time to share this! Hearing that it’s helping you stay organized right away means a lot. If you encounter anything you'd like to see improved as you use it more, I'd love to hear your thoughts