Keep what matters.
Feed, channels, polls, conversations. Turn each module on or off. Build around your people, not a feature checklist.
Explore the modulesIts own address. Its own brand. Its own members.
One platform underneath, and only the parts you need.
Private and unindexed until you decide otherwise.
Good communities don’t need more software.
They need the right space to come together.
Feed, channels, polls, conversations. Turn each module on or off. Build around your people, not a feature checklist.
Explore the modulesYour colours, your domain, your words. Call them channels, rooms, or circles. It should feel like you live here.
Make it your ownOne deployment, any number of communities. Each one a database row. Nothing about starting another needs an engineer.
Meet the foundationA community is a row, not a deployment.
Nothing about starting one needs an engineer.
your-community.success.digitalcommunity.yourdomain.comNo deploy, no developer, no ticket.
Try it on the community below.
Day rate or project fee? Eleven years in and I still change my mind depending on the client.
The part nobody warns you about is how much of this job is writing things down before anyone asks for them.
Best lead this quarter came from a client I lost in 2019. Leave on good terms. Always.
Both of those are settings on a row, not a deploy. Harbourline is our demonstration community — a fictional brand with sample content, kept private and unindexed.
Most platforms ask you to trust the interface.
These three rules live in the database instead.
Not a setting and not a promise in an interface. A conversation id is not an invitation, conversations are scoped to one community, and notifications carry who wrote — never what was said.
A new community starts private and off the search engines. Being readable and being indexable are two separate switches, and both of them are yours.
One queue for reports and join requests, oldest first, with an audit log behind it. Moderation you can account for later.
A name for your community. An address to call your own.
Choose a starting point and the modules that fit your purpose.
Pick an accent. Name your channels. Open the door.
Live means in production now.
In build means in active work. Nothing else is on this page.
Events, courses and payments are designed and not decided. When they are built they will appear in the left column, not this one.
No. A community is a database row rather than a separate install, so naming it, branding it, choosing its modules and picking its theme all happen in settings. Nothing waits on a deploy.
Yes. Your community starts at an address on success.digital and moves to a domain you own whenever you are ready. Today that is a short step with us rather than a self-serve field, and your original address keeps working until the new one is verified.
Not unless you say so. New communities start private and unindexed. Being readable and being indexable are two separate decisions and both belong to the host.
A host cannot, and neither can a platform administrator. The rule is enforced in the database rather than by the interface, and message notifications record who wrote without recording what was said.
Every module switches on or off per community — feed, channels, members, conversations, polls, questions and commitments. Turn off what your people will not use and it stops existing for them.
Pricing is not settled. The tiers on the pricing page are illustrative placeholders rather than available offers, there is no billing in the product, and nothing is charged when you create a community.
Meet Success.Digital. Make it your own.