Talk to the people who build it
SurfSense is a small team, so there is no ticket queue and no contact form that goes nowhere. Pick whichever of the four below matches what you need.
Where to write
Four addresses, each for a different kind of message. A bug report sent to a sales call helps nobody.
Licences and rollouts
Book a call
Thirty minutes with the person who builds it. Best for team licences, procurement questions and deciding whether SurfSense fits how your team already works.
Anything else
Send an email
Licence keys, invoices, partnerships, press, or a question that does not fit anywhere else. We read every message and usually reply within one business day.
Bugs and feature requests
Open a GitHub issue
Something broken, or something missing? File it on the repository so it is tracked in public, next to the code and the release it ships in.
Help and ideas
Ask the community
Setup questions, model choices and workflow advice get answered fastest in Discord, where other people running SurfSense locally can weigh in too.
Reporting something broken
SurfSense runs on your machine, which means we cannot look at your logs, your index or your model settings. Everything we know about a bug is what the report tells us.
Four details turn a report into a fix rather than a round trip. Nothing here asks for your documents. Describe the failure, not the file it happened on.
Enterprise, volume and procurement
Above 25 seats, or where security review, invoicing and purchase orders are part of the process, the published pricing stops being the whole answer. Write to rohan@surfsense.com with your seat count and what your procurement team needs, and you will get a reply from a person rather than a form.