Help & legal
Collabea is an alpha. Here is what works end to end, what is a preview, and what shows sample data.
Collabea connects brands with content creators across seven disciplines: influencer marketing, UGC, video production, editing, photography, graphic design and social media management. A brand posts a job, creators apply or get hired directly, and the work runs through a contract with milestones, deliverables and payment.
This deployment shows the whole product, including the parts whose backend is not finished. Each of those is labelled where it appears: Preview for built screens without a live service behind them, Sample data for real screens showing illustrative numbers. The lists below match those labels.
Real API, real database, real sockets. You can run a job from posting to a paid contract.
Email sign-in on an httpOnly session cookie, email verification and OTP password reset, multi-account switching in one browser, and revocable sessions per device. Google sign-in is built and appears where the deployment has credentials.
Seven service categories, each with its own validated config, rate cards, milestones and deliverable schedules.
Apply, counter, request changes, withdraw and reapply, with the full proposal history kept.
A brand sends an offer to a specific creator. Accepting it is consent-gated and creates the contract.
Milestones, deliverables with revision rounds, shipments, reviews, disputes and cancellation.
The free-beta handshake: the brand marks a milestone paid, the creator confirms receipt, and both sides are timestamped, with reminder sweeps and a not-received flag.
Real-time chat over Socket.IO with file attachments, replies, reactions, and contract cards that update in place.
In-app and email, ten preference families, and a per-category opt-out that is honoured.
Provider profiles, portfolios, service rate cards, and search and filtering across the marketplace.
Ranked server-side on eight weighted factors over real profile data, with the breakdown behind every number and the same rules run both ways: creators against a brief, and open jobs for a creator. Retrieval is lexical. A ninth, semantic-fit factor joins only where an embedding driver is configured, and the other eight are rescaled around it.
Group campaigns with participants and payouts, and creator events with responses.
Finished and interactive, one step short of live. Some have no service behind them; others are wired and waiting on a credential or a model.
Fund, release, refund and Connect onboarding are implemented and open read-only from any contract's milestones, marked as a demo. They stay read-only because the platform holds no money during the alpha and this deployment carries no Stripe credentials. One config flag switches the rail on.
Rewrite, expand, shorten, proofread and draft from scratch all call a server route that streams its answer back token by token. Three drivers sit behind one contract (a simulated one, plus real Anthropic and OpenAI ones) and share a gateway with a daily token budget, a response cache and a usage ledger. The default is the simulated driver, so the text here is an authored, provenance-stamped fixture; a model key is the only switch. A provider named without its key answers 503 rather than quietly serving a fixture.
Plans a campaign and runs it step by step, with every run and step recorded in the database. A step that would send or create something halts for your approval and cannot pass without one; approving twice conflicts rather than running twice. What the steps produce is illustrative and nothing reaches a creator.
Suggests service packages and prices from what your profile already says. It runs entirely in the browser, with no model and no server, so treat the numbers as a starting point to edit rather than a market rate.
Prompt, references, sizes, variants and attach-to-brief are all built. With no image model configured the tiles are sample photographs from the app's own library, each stamped as one. Where a deployment has a model, the studio calls it and every label follows the tiles.
Your intent is parsed server-side: budget, timeline, platforms and counts come out of the sentence. The wording around them is an authored template, not a model, and every row in the diff says which of the two it came from.
The MCP server an outside AI client connects to is implemented: bearer auth, seven tools, a scope check on every one, and no tool that moves money, signs a contract or touches a dispute. Settings mints a real per-user token, shows it once and keeps only its hash. A missing or invalid token gets a 401. Two of the five scopes are reserved, no tool answers to them yet, and the screen says which.
Designed, not staffed. Email reaches a person today.
Submitted tickets are stored in your browser, not sent to a queue.
The settings screens are built. The enforcement behind them is not wired yet.
Profile visibility, messaging permissions and search privacy are labelled previews. They are kept in your browser tab and nothing enforces them yet.
Compose once, customise per network, preview in each platform's frame, then schedule, queue or post now, with brand approval on contract-linked posts and the disclosure rules (FTC, ASA, ASCI) checked on every caption. Posts, channels and approvals are saved to your account and notify the other party. Publishing itself is simulated: the platform app reviews that unlock real publishing have not been filed, and the composer says so.
Creators link Instagram, Facebook, YouTube, X and TikTok through each platform's official API, and the OAuth flows are implemented. This deployment carries no platform API credentials yet, so the Connect buttons say so.
Image and video generation with presets, per-shape controls, a cost shown before you commit, a daily allowance, and every outcome a real generator has: queued, generating, partly ready, declined, failed, stopped. No image or video model runs. Every result is a sample photograph from the app's own library, stamped as one, and work that produced nothing is never charged.
Real components and real code paths, showing illustrative numbers.
Sample creator profiles across seven disciplines, jobs and campaign pools let you explore the product. The showcase changes as profiles and listings are added or removed.
Balances, invoices, payout accounts and saved cards are illustrative. No money moves through the platform during the beta.
The charts are real components drawn against demo figures.
The calendar opens with sample posts in every state (drafts, awaiting approval, scheduled, failed, verified) and sample performance figures, each stamped. Your connected channels are real; the sample channels beside them say so.
Every tile the Studio produces is a photograph the app already ships, picked from the prompt and stamped “Sample imagery”. The library opens with past runs in every state, so the unhappy ones are visible without causing them. No creator's portrait is ever presented as generated output.
Verification pages read from a fixture set. An unknown code returns no record rather than a made-up one.
A logo catalogue and a static status dot, both labelled in place.
The platform charges no fee and holds no funds during the alpha. Brands pay creators directly, and the platform records a two-sided handshake per milestone so both parties have a timestamped record. That rail is live, and it is the one real contracts run on here.
The Stripe escrow rail is the alternative, where the platform would hold the money until deliverables are approved and then release it. It is built (funding, release, refund, Connect onboarding, webhooks) and its screens open from any contract's milestones, marked as a demo. They stay read-only: the platform holds no money during a free beta, and this deployment carries no Stripe credentials.
Two repositories, with typed contracts enforced on both sides of the wire.
Questions, data requests or something not working? Email support@collabea.com. It reaches a person.
Answers to common questions are in Help and support.