Using SupaNet
What SupaNet can do for you, in plain language. No code required.
This section is for everyone who logs in to SupaNet to get something done. You do not need to know how it is built, and you do not need to write any code. The goal here is simple: show you what is possible so you can reach for the right feature at the right moment.
What SupaNet actually is
Think of SupaNet as a private place for your team that comes with a very capable assistant. The assistant lives in the chat, but it is wired into the rest of the workspace, so it can do real work and not just talk.
A few things make it different from a generic chatbot:
- It can read the files and PDFs your team uploads and answer questions from them, with citations.
- It can save documents, code, and web pages as shareable "artifacts" you can send to anyone with a link.
- It can run tools (look something up on the web, send an email, call a custom function your team set up).
- It reacts to things happening in other systems through webhooks, so it can work even when you are not watching.
- It is private by default - the database itself enforces who can see what.
The main pieces
The chat assistant
Where you talk to SupaNet, attach files, and get work done.
Artifacts
Save and share documents, code, and live web pages with a link.
Files & knowledge
Upload files and PDFs, then ask questions of them.
Skills & prompts
Reusable shortcuts and the always-on rules that shape the assistant.
Automation
Let SupaNet react to events and run on a schedule.
What's possible
Real things people use SupaNet for, to spark ideas.
A quick mental model
Most of your time is spent in the chat. From there you can pull in knowledge (files and PDFs), produce something you want to keep or share (an artifact), or lean on a shortcut someone set up for you (a skill). Behind the scenes an admin decides which tools and rules are turned on for the whole workspace. That is the whole thing.