Vakh Start on Vakh

Vakh for builders

Build something useful.
Help it grow.

Make a tool, resource or shared space with Vakh. Put it in the hands of people who need it, and keep making it better together.

Part one

Build

Start with a real problem and make one useful thing work.

Choose who you are building for

A club that needs a place for submissions. Students looking for reliable campus information. A team whose research gets lost in chat. Pick something you understand, and speak to the people who would use it.

Vakh is a social app built around structured posts. Forms define what people can contribute; views turn that content into feeds, galleries, calendars, maps and more. Build directly in the app, or use code and MCP to connect an AI assistant to the same content.

Ideas to start from

  • A campus guidePlaces, timings, tips and useful links that students can keep up to date.
  • A shared resource libraryTools and learning resources people can browse, contribute to and return to.
  • An AI research logAn assistant saves findings with sources, while people explore and discuss the results.
  • A submissions spaceCollect writing, project demos or event entries, then give them a place to be seen.

Explore more possibilities:

Make it usable

Create the forms you need, choose views that help people find their way, and decide who can read and contribute. Keep the first version small enough that someone can complete a useful task. Let them try it, listen to what gets in the way, and improve it.

Learn the Vakh basics

Building with AI or code?

Connect a client that supports remote MCP with OAuth to https://xo.vakh.com/mcp. Use Streamable HTTP, sign in with your Vakh account and approve access.

Your assistant can read forms you own or follow, create or update authorised posts, and query the data. Start with one complete workflow, such as saving research with sources or summarising a shared board.

Account setup, following, sharing and badge membership stay in the app. Add media and files there too. Your assistant works within your permissions.

Read the MCP documentation

Part two

Grow

Bring people in and give them reasons to keep participating.

Share it with people who need it

Invite a few people who have the problem you are solving. Share your Vakh profile, form or post, explain what they can do, and help them get started. Ask for feedback and use it to shape what you build next.

All useful contributions count

Growth includes what you contribute yourself, how people respond to your work, and what the people you bring to Vakh go on to do across the platform.

  • Your participation. Keep posting useful things, respond to others, give feedback and Hearts, and take part in the spaces you care about.
  • The response to your work. People read, return, reply, contribute and give Hearts to what you share.
  • The people you bring in. Their posts and interactions count too, along with following forms, connecting with others and coming back to use Vakh.

These contributions can happen in your own space or elsewhere on Vakh. Help people find something they want to keep doing.

Keep it useful

Notice which tasks people complete, what they contribute, and what brings them back. Keep information current, welcome new contributors and make improvements from their feedback. A small space that people use regularly gives you something to build on.

Judging

What wins

A useful, working project and real participation on Vakh.

Build

  • Usefulness. A clear audience and problem, with a practical benefit for the people using your project.
  • Execution. A complete, usable workflow. Forms, views, permissions or integrations help someone finish a real task.
  • Use of Vakh. A thoughtful approach that makes meaningful use of Vakh and improves through user feedback.

Grow

  • Useful contributions. Helpful posts, feedback and interactions from you and the people you bring to Vakh, across the platform.
  • Real adoption. People get started, use what you built and take part. The quality of participation matters alongside its reach.
  • Reasons to return. Continued usefulness through repeat participation, fresh contributions or improvements that address user needs.

Judges consider both Build and Grow. Projects built directly in the app and coded or MCP integrations share the same objectives. Complexity, signup totals and reaction counts alone do not determine winners.

Show your working project, who it helps and evidence of real use, contributions and feedback. Explain what you improved and separate observed results from future plans.

Download on the App Store Get it on Google Play Start building