Innerloop
Read-and-acknowledge receipts and a feed every shift worker can reach, without a company email — what Workvivo starts selling at $20,000 a year.
Innerloop is a company-branded internal social network and communications hub, built mobile-first to reach the deskless and frontline majority — retail, healthcare, hospitality, manufacturing — as well as office staff.
You can name the people who have not read the policy yet.
Internal communication is usually measured by what was sent. A notice goes to everyone, engagement is reported as a percentage, and the question that actually matters — did the twelve people this concerns see it — has no answer. It stays theoretical until something goes wrong on a shift and somebody asks whether the person had been told. At that point the honest answer is that a message was published, which is not the same thing, and everyone in the room knows it.
- Frontline tasks & must-reads
- Advanced reach analytics
A store associate reads what concerns their store, on their own phone.
Most internal tools are built for the head office and handed to the frontline afterwards. The result is a feed full of material about departments the reader has never met, arriving on a channel that assumes a company laptop and a work email address. Frontline staff stop opening it within a month, and the company concludes its people are disengaged rather than that it has been broadcasting to the wrong audience on the wrong device.
- Social feed + reactions/comments
- Web push (OneSignal)
Every new hire gets the same onboarding whether or not their manager is free.
Onboarding quality tracks manager availability, and nothing else. A hire who starts in a quiet week gets the tour, the context and the introductions; one who starts during a launch gets a laptop and good luck. The difference shows up months later as uneven ramp times and early attrition that gets attributed to fit. Nobody connects it back, because by then the two weeks that caused it are long forgotten by everyone except the person who lived them.
- Learning paths
- Surveys / eNPS / polls
Delivery and reading are tracked per recipient, per channel:
Aggregate counters are maintained on the announcement itself by database triggers, so the reach dashboard reads a number rather than counting rows. On a 20,000-employee announcement that is the difference between a dashboard and a timeout.
Fan-out to recipients runs through a job queue in batches rather than in the request that published the announcement.
Posts paginate on a cursor rather than an offset, which is what keeps a long feed stable while new content arrives at the top.
Feed content is served over a cacheable short poll rather than a per-user realtime subscription. This is a deliberate engineering choice with a commercial consequence: a per-user subscription for every employee in a 2,000-person company is thousands of concurrent connections to carry a feed that changes a few times an hour. A "new posts" banner arrives either on the poll or on a single shared per-company channel — never one subscription per person.
Included on every tier. Recognition is the feature that gets a quiet feed moving, so gating it would undercut the rest of the product.
Messages persist through the database's own change stream rather than a broadcast channel, because a chat message that exists only in transit is a chat message lost on reconnect.
Messages persist through the database's own change stream rather than a broadcast channel, because a chat message that exists only in transit is a chat message lost on reconnect.
For a frontline workforce this is often the most-used screen in the product — it answers "who is the duty manager at the other site" without a phone tree.
Three specific things, because the phrase is otherwise decoration:
Web push as a first-class delivery channel, since a deskless employee does not have a mail client open.
Installable, with the feed readable offline. The app installs to a home screen and carries a service worker, so the feed is readable in a stockroom, a basement or a ward with no signal. Composing offline and syncing later is deliberately not in this version — reading is the case that matters, and half-working offline writes are worse than none.
eNPS responses are anonymous, and the score is calculated over them. That anonymity is load-bearing: a sentiment survey attributable to the person who answered it measures how safe people feel, not how they feel.
The same delivery and targeting machinery the announcements use applies here, so a learning path can be assigned to a segment rather than to a list of names pasted from a spreadsheet.
The platform underneath the product — counted in this product's own source, not claimed from a template. Where a row carries a list, open it to read the names behind the number.
Coinbase
dLocal
Flutterwave
Komoju
Mollie
NOWPayments
Opn
Paystack
ActiveCampaign
Customer.io
Segment
Canny
Amplitude
Custom Head Scripts
Pushover
Twilio SMS
Crisp
Tawk.to
Monday.com
fal.ai
Axiom
hCaptcha
Freshsales
Pipedrive
Pabbly Connect
AWS S3
MuxHover a table to isolate what it touches; click one to read its relationships. The big nodes are what everything else hangs off. organizations is referenced by 65 tables because every single record in this product belongs to an organization, and that is what makes tenant isolation a property of the database rather than something the application has to remember on every query.
all 78 tables, as text
active_boosts · admin_notifications · analytics_daily · analytics_events · analytics_funnels · announcement_dismissals · announcements · api_key_logs · api_keys · assistant_actions · assistant_conversations · assistant_messages · assistant_usage · audit_logs · automation_log · automation_templates · badges · content_announcement_deliveries · content_announcement_reads · content_announcements · conversation_members · conversations · credit_balances · credit_transactions · currencies · data_exports · data_imports · faq_categories · faq_items · feature_flags · inbound_webhook_events · inbound_webhooks · languages · learning_assignments · learning_item_completions · learning_items · learning_paths · marketing_audience_members · marketing_audiences · messages · notification_log · notification_rules · notifications · organization_limit_overrides · organizations · plans · platform_secrets · platform_settings · post_comments · post_reactions · posts · product_purchases · products · provider_prices · push_devices · recognitions · report_templates · roles · scheduled_tasks · segment_members · segments · seo_meta · space_members · spaces · subscriptions · survey_questions · survey_responses · surveys · task_assignments · tasks · theme_page_sections · theme_section_library · theme_sections · translations · user_sessions · users · webhook_logs · webhooks
The chassis, and anything particular to this product. 6 required, 2 optional.
No platform lock-in.
Postgres with row-level security, applied by the shipped migration scripts.
Per-seat subscription quantity. Configured by the operator, not hardwired. A provider without native per-seat quantity falls back to a standard subscription.
Announcements, digests and notifications.
The primary channel for deskless staff.
Announcement fan-out runs in batches outside the publishing request. Without it large sends will not complete.
Only if the SMS delivery tier is enabled.
Employees load by CSV; per-organization credentials for it are stored encrypted.
Already built — plug and play
Every provider integration in this list ships wired into the product. You bring your own keys, connect them in the admin, and go live — there is no integration code to write. Nothing is resold through us: the ongoing cost is whatever these providers charge you. Capabilities marked plan-gated elsewhere on this page unlock by plan, not by extra code.
What exactly do I receive after purchase?
The complete source repository behind the live demo — 141,438 lines across the application and its database, 78 tables defined by 85 migrations that the shipped scripts apply for you, plus the seed data, the demo accounts and the setup documentation. Not a subset and not a scaffold: the same code that runs the demo you just used.
Is the live demo the same product whose source I receive?
Yes. The Innerloop demo runs the delivered release (v1.0.0), and the build figures on this page are measured from that same source — not from a showcase build kept separately.
Can I test every account role before buying?
Yes — all 4 of them: Employee, Editor, Company admin, Platform admin. Each one is seeded in the live demo and reachable from the role board above, so you can inspect the product from the customer's side, the agent's side and the administrator's side before you decide.
Is this a complete product or a starter template?
Complete. 96 page modules and 312 HTTP operations, with authentication, roles, billing, an administration panel, background jobs and seeded demo data all wired and running. A template gives you the shape of an application; this is one you can deploy and start operating.
Can I rebrand and modify it?
Yes, without asking. The name, identity, copy, styling and code are yours to change. Rebranding and operating it as your own service is exactly what the licence is for.
What does the licence allow?
A perpetual, worldwide, non-exclusive, non-transferable licence to the product you bought and to every update released for it. The Standard licence covers one business — yours. If you deploy for clients, the Client licence covers up to five. You can modify it, rebrand it, deploy it and charge your own customers.
Can I resell the source code?
No. Reselling, redistributing, sublicensing or giving away the source itself is not permitted under either licence. You build and deliver products with it — the code stays with you.
What services and ongoing costs are required?
You bring your own accounts, so we never mark anything up and there is no ongoing cost to us beyond the purchase. Required: Node host, Supabase, A payment provider, Email provider, Web push provider, A job queue, Roster import. Optional: SMS provider. The table above says exactly what stops working without each one; most have usable free tiers at low volume.
How difficult is deployment?
Two ways, and most buyers use the first. The installer in your saascode dashboard walks it: you create free accounts at Vercel and Supabase, connect them, and it provisions the database, applies 85 migrations, seeds the data, deploys and verifies the result — you watch the steps go green. Or take the source and do it yourself with the shipped scripts and docs, which is the same sequence run by hand.
What updates and support are included?
Updates to that product for as long as we maintain it — no renewal fee and no expiry date on your access. Support covers download problems, defects in the code as shipped, questions about what the product does and how it is structured, and licence questions. It does not cover debugging your own modifications, building features for you, or setting up your hosting and third-party accounts.
Why does a complete codebase cost $299?
Because it was built once and is distributed many times. SaaSCode builds each product and ships the same finished release through the catalog, so the price reflects repeatable distribution — not a reduced codebase, an unfinished template, or what the same work would cost commissioned.
Do I need to be a developer?
No, for the normal path. You create free accounts at Vercel and Supabase, connect them to the installer in your saascode dashboard, and it does the deployment for you — provision, migrate, seed, deploy, verify. What it asks of you is creating two accounts and copying a token, not writing code. If you would rather deploy it yourself, or host it somewhere else, the full source and the scripts are yours to do that with. Running the product day to day needs no technical skill at all: that happens through its own interface, which is what the demo shows.