Introduction
What Impact Hub OS is, who uses it, and where to find what you need in these docs.
Impact Hub OS is the Support Stack platform for Impact Hub Houston. It is the place where founders, mentors, volunteers and partner organizations join the network, get matched with each other, book office hours, and show up for events.
Production is at www.impacthubos.com. This site documents how it works, how to run it, and how to change it.
The Three Pillars
- Matching, Onboarding and Pooling. A single intake form brings every kind of member in. Approved applicants are invited, their answers become their profile, and the matching engine proposes mentors to founders based on what each said they need and can offer.
- Volunteer Onboarding. Volunteers say what they can help with and when. Events list what they need, volunteers raise a hand, and organizers see the roster fill.
- Office Hours, Scheduling and Video. Mentors publish availability. Founders search for a mentor in plain language and book a session. The session lands on both calendars with a video link.
Around those pillars sit the things every member uses: a calendar of everything that concerns them, a directory, a library of tools and templates, partner offers, and an Overview that tells each person what is next and what is waiting on them.
Who Does What
| Role | What they do on the platform |
|---|---|
| Admin (Impact Hub Houston staff) | Review applications, invite people, manage members and roles, run events and matching, edit the words the platform sends and the questions it asks |
| Founder | Describe the business, take the assessment, get matched, book office hours, attend events |
| Mentor | Describe what they can help with, set availability, accept matches, hold sessions |
| Volunteer | Say what they can help with and when, sign up for event roles |
| Investor | Describe a thesis; founders who fit can reach them |
| Partner | Represent an organization: its profile, its people, its listing under Partners, and the resources it shares |
A person can hold more than one role. A founder who also mentors sees both sides.
Where to Go
- New to administering the platform: start with How the Platform Works and Navigating the App, then the Admin Guides.
- Looking after the services and the code: Tech Stack, For Developers, and the Runbooks.
- Something is wrong right now: Runbooks first, then the FAQ.
- Pointing an AI coding agent at the codebase: Working With AI Agents.
Conventions in These Docs
Labels in bold are the exact words on screen. Paths like /settings/members are addresses inside the app. Names in code are files, variables or commands. Secrets are never written here; variable names are, values are not.