On your server: API, panel, database and cache. Object storage, email delivery, push and the bot check run on external services on your own keys; member data never leaves your server.
On-prem, white-label B2B matchmaking platform
A closed, invite-only B2B meeting platform for your members, on your own server.
It brings the members of your association, chamber, technopark or event together in a closed circle; finds the right person and company with a reason, makes the connection, opens the conversation and books the meeting on the organiser's schedule. All of it on your server, under your brand.
One install, one organisation: code and data on your server, the app on the stores under your name.
- Invite
- Group
- Discover
- Connect
- Message
- Meet
The main loop: from the invite list to an accepted meeting, in six steps.
Lonca in numbers
5
Matching signals with fixed weights; the reason on screen
163
Bilingual starter terms across 7 glossary types
100
Numbered tables at most, guaranteed by the database
6
Ready Excel reports, built in a separate server process
47
Help desk articles, opened on top of the work
2
Years of audit log; 1 year of email delivery ledger
Sound familiar?
Five desks, five sentences, five mechanisms.
Each one is a sentence we heard from a general secretary, a cluster manager, a fair organiser, an IT lead or a member; opposite it, the product's answer.
WhatsApp groups, Excel lists; at the annual summit nobody knows who met whom.
Invite-only matching groups, suggestions that state their reason, recorded meetings and six ready Excel reports: group participation, activation funnel, connection and meeting logs, company summary, unmet demand.
On the big networks everyone writes 'software'; nobody can tell who sells what to whom.
Services offered and services sought come from one bilingual glossary; complementarity (you seek, they offer) ranks before similarity.
Paper appointment slips on fair day, tables double-booked.
The organiser writes the schedule: sessions, meeting length, breaks, tables. Two meetings at the same table at the same time are impossible by the database's unique index.
We do not want to hand our member data to a cloud SaaS.
One Linux server, no Docker; code and data with you. Four external services, delivery only, on your own keys. Audit log, delivery ledger, scheduled backups to your own bucket.
A directory full of names, spam connection requests.
A member sees only the people and companies in their own groups; no message until a connection is accepted; contact details are off by default.
Why Lonca
Six claims, all six tested against the code.
Every sentence on this page was verified in an end-to-end scan of the codebase; what could not be verified was left out.
Invite-only, closed, filtered on the server
There is no public sign-up; an address no admin put on a list cannot open an account. Person, company, message and meeting queries are filtered on the server by the member's group membership; a profile outside the group is never returned.
The schedule is a rule, not a suggestion
Sessions, meeting length, breaks, blocked days, a daily cap and the allowed meeting types are the organiser's; all three write paths go through the same gate, and an off-grid time such as 09:07 is rejected.
Numbered tables, guaranteed by the database
TABLE-1 to TABLE-100; a member choosing an on-site meeting picks from the tables free at that time. Two accepted meetings at the same table at the same time are impossible by a partial unique index.
The company column becomes a record, a human decides
A Turkish-aware matcher that drops legal suffixes ranks the existing records; only an exact match is pre-selected, a close one is shown, the choice stays with the admin.
Suggestions state their reason, not a percentage
'Offers what you seek: Cloud, ERP'. Five signals are scored with fixed weights; because the glossary is bilingual, a member reading Turkish and one reading English match without translation.
An ordinary Linux server you own
Three PM2 processes behind Caddy, MongoDB and Redis as plain installs, no Docker. A misconfigured production start refuses to boot.
Smart matching
Matching that states its reason.
Today the matching is an explainable, deterministic rule, not a learning model: five signals, fixed weights, the reason on screen. Instead of a black-box score, the member sees the answer to 'why this person'.
Five signals, fixed weights
Offers what you seek (4), seeks what you offer (3), shared collaboration interest (2), shared talking point (2), shared interest (1). The score saturates at 0 to 100; with no overlap at all, no suggestion is made.
One glossary, two languages
Service, collaboration interest, interest, talking point, sector, product type and tag: 163 starter terms come with Turkish and English names. Admins edit them, members propose missing ones, no duplicates form.
Search that gets Turkish right
Letter folding on every path: 'Işık', 'Bilişim', 'Sarnıç' slip through a plain database search and are found here.
Find similar companies and merge
The same matcher scans the whole list, turns three spellings into one group and proposes which record survives; the surviving profile is kept in full, people and decided requests move over.
There is no learning model, embedding or semantic search; when the AI steps on the roadmap enter the product the page will say so, and not before.
Meeting schedule and tables
One table, one time, one meeting.
The organiser writes one schedule per group; the member's request, a reschedule and the organiser's assignment all pass through the same gate. An off-grid time is rejected, a taken table says 'table full', an accepted meeting lands in both calendars.
The schedule is the organiser's
Up to 12 sessions; slots of 5 to 480 minutes, breaks up to 240 minutes, weekdays, blocked dates, preparation time, a daily cap (up to 100), allowed meeting types. A live grid preview in the panel.
Four meeting types
In person, online, phone and on site (fair floor). For an on-site meeting the member picks from the tables free at that time; the table prefix and count are the organiser's.
The invitee's calendar rejects, the inviter's warns
Only an accepted meeting blocks a slot; pending requests cannot empty a rival's fair. In a multi-party meeting, an answer per seat.
Lands in the calendar, reminds
An accepted meeting is written to the phone calendar, updated, deleted; an .ics fallback. Reminders 24 hours and 1 hour before; an organiser's assignment of 2 to 20 people counts as accepted on arrival.
For members
Nothing to learn, a flow to follow.
The iOS and Android member app, five tabs, one loop: Meetings, People, Companies, Messages, Profile. First sign-in, the consent gate and the profile are done in three screens.
No password
A six-digit code by email: valid for 10 minutes, 5 attempts, 60 seconds between resends. An uninvited address lands on a calm explanation screen, not an error.
Only your own group
People and companies are filtered on the server by group membership. Filters: group, connection status, interest, topic, sector, services offered and sought.
Suggestions with a reason
The 'For you' tab shows common ground first: who offers what you seek, who seeks what you offer, shared topics and interests.
No message before a connection
Live messaging opens once a connection request is accepted; group rooms, archiving, muting (8 hours, 1 week, forever), read receipts. Block and report.
Schedule grid and tables
With a schedule, times come from the grid; on site, from the free tables. A meeting request shows as a line inside the chat.
Lands in the calendar
An accepted meeting is written to the phone calendar; an .ics fallback; reminders 24 hours and 1 hour before. Member-to-member traffic is never email, so it never fills your inbox.
Digital business card
A QR code and a 24-hour share link; save to phone as a vCard. Contact details show only if the member allowed it and the connection was accepted.
Delete your own account
A 30-day grace period: hidden from everyone at once, closed on day 30, cancellable in the app in between. Five privacy switches in the member's hands.
For admins
The panel works like a desk.
Records open as windows on top of the list, shrink to the dock, and the stack of open windows is written to the address bar and shared as a link. Ctrl+K reaches 12 pages and eight record types in one keystroke.
Upload the Excel, re-upload as often as you like
Rows are updated by the (group, email) pair; a re-upload sends nobody a second invite. Seven columns in Turkish or English, in any order. 5,000 rows per request.
The company column becomes a record
The matcher drops legal suffixes and ranks existing records; an exact match is marked, a close one is shown, the admin decides. The linked person becomes the company's editor, not its owner.
Schedule and tables, with a live preview
Per group: sessions, length, breaks, allowed types, table prefix and count; the grid is drawn live in the panel. Organiser assignments pick from tag-filtered people.
The help desk on top of the work
47 articles on 6 shelves, a search that folds Turkish accents; a link inside an article does not close the guide, it drops to the dock and reading resumes where it left off.
Six reports, two ledgers
Group participation, activation funnel, connection and meeting logs, company summary, unmet demand: Excel, kept 30 days. Every admin write in the audit log (2 years), every outgoing email in the delivery ledger (1 year, the body never stored).
bilisim
Pages
Records
Group · Summit 2026
ActiveMatching group · 12 to 13 March · 184 invited, 131 active
Member: Deniz KayaCompany: Bulut Bilişim A.Ş.Meeting: TABLE-7 09:20
A summit's calendar
From the list to the table, thirty days.
Every step is real product behaviour; the days are an example, the rules are the system's defaults.
- 30 days before01
The list goes up
The admin opens the matching group and uploads the Excel; the invite email goes out under the association's name with two store links and the group's dates.
- 23 days before02
Reminder
An automatic reminder to those not yet active after 7 days; a 2-day cooldown for manual ones. Imported / active / rate in the panel.
- 14 days before03
Profile and discovery
The member signs in with a code, passes the consent gate, fills the one-step profile; the directory and profiles stay open outside the group's dates, so preparation starts weeks ahead.
- 7 days before04
Connections and requests
Connection requests from the 'For you' list; messaging once accepted; meeting requests from the organiser's grid.
- 1 day before05
The schedule fills
The organiser fills the remaining gaps by assignment; reminders go out 24 hours before.
- Event day06
Tables
On-site meetings at numbered tables; a reminder 1 hour before; cancel and reschedule through the same gate.
- Day after07
Reports
Group participation, connection and meeting logs, unmet demand: Excel, with a cover sheet.
- Nightly08
Backup
A full database archive to your bucket at 00:00; a report email to everyone who is an admin, on success and on failure.
Member app
Members are mobile only; on the stores under your name.
One app for iOS 15+ and Android 7+; published on the organisation's own Apple and Google accounts, with its own logo and palette. The web is the admin's.
Five tabs, one loop
Meetings is the default: the next meeting as one card, requests awaiting an answer, what is coming up. People, Companies, Messages, Profile.
Consent gate
Before any personal data is asked for: the user agreement, the privacy policy and the data notice; which version was accepted and when is recorded, and a material change reopens the gate.
Notifications in the member's hands
9 categories, each with a push and an email switch. Message, connection and meeting notifications are never email; chat notifications are batched in a 5-minute window.
Turkish first
Turkish and English, 844 strings per language, parity tested; follows the device language, can be set by hand. Accessibility: WCAG AA colour, badges announced to screen readers.
There is deliberately no offline cache; a quiet notice card appears without a connection.
Meetings
- Meetings
- People
- Companies
- Messages
- Profile
White label
Your brand, in three layers.
One install is one organisation; white label means an install and a rebrand for one organisation. What changes from the panel, what by configuration and what in code and assets is kept clearly apart.
No code, from the panel
- Groups and four feature switches, date windows
- Meeting schedules: sessions, length, breaks, tables
- Lists, tags, company records and roles
- 7 glossary types, bilingual
- Legal texts (versioned), FAQ, announcements
- Backup policy, theme
No code, by configuration
- Sender name, address and delivery keys
- Storage account and bucket
- Push and bot-check keys
- Domains, JWT lifetimes, sign-in code rules
- IP ban thresholds, support email
Code and assets, once per organisation
- The vector logo goes in once; 9 marks are generated and distributed
- The palette is derived from one brand colour, light and dark theme
- Product name, copy, email and notification wording
- The mobile app on the organisation's store accounts
- The starter glossary re-curated for the sector
Internative sets up the code and asset layer; as the team that builds the product, it also adapts it at code level to your needs, from the same hands.
Who it is for
Any organisation that has to bring its members together.
The common thread is the same: a closed circle, finding the right person and tying that meeting to a schedule. From a single summit to networks open all year.
Technoparks and technology development zones
A company directory by services offered and sought; suppliers and buyers matched by complementarity.
Business development communities
Groups open all year, connections and messaging; members carry their network in the app.
B2B matchmaking events and fairs
Meeting schedule, numbered tables, organiser assignments; the reports the day after the event.
Associations and chambers
An invite-only member circle, introductions before the general assembly, sector groups; from an Excel list to a live install.
NGOs and foundations
A volunteer and stakeholder network in a closed circle; personal data behind a consent gate, on your own server.
Clusters and industrial zones
Supply matching between participant companies; similar company records merged.
Investor networks and accelerators
Investor, participant and exhibitor tags; meeting assignments filtered by tag.
Exporter unions and trade delegations
A schedule grid and tables for the buyer delegation day; matching without translation through the bilingual glossary.
On-prem and security
Code and data on your server, four external services on your keys.
An ordinary Linux server you own: three PM2 processes behind Caddy, MongoDB and Redis as plain installs, no Docker. One deploy script, a health-gated reload, a smoke test over real HTTPS.
On your server
- Admin panel and marketing site (Next.js, PM2)
- API (NestJS, PM2) and the report worker
- MongoDB 7 and Redis 7, plain installs
- Caddy reverse proxy, TLS
- Backup archives to your own bucket
- Health endpoint: database, cache, mail, queues and index count
Outside, on your keys
Four of them are for delivery; member data stays on your server. Maps is a place picker only and optional.
- Object storage: a private S3-compatible bucket (reference: Cloudflare R2)
- Email delivery: Cloudflare Email Service, on the organisation's domain
- Push: OneSignal (over APNs and FCM)
- Bot check: Cloudflare Turnstile (admin sign-in)
- Map tiles: Google Maps (optional)
Passwordless sign-in, a separate admin gate
Members by email code; admins through a separate gate with a bot check, answered the same way for every address. IP ban: 30 failures in 10 minutes, blocked for 15. Rate limits per account; a fair hall's shared network is not one quota.
Group scope on the server
Test suites that never widen the scope for people and companies. Only four public routes carry member data, and each is bounded by an unguessable, expiring value.
Two ledgers, two retention periods
Every admin write in the audit log with a before/after diff, 2 years. Every outgoing email in the delivery ledger, the body never stored, 1 year.
Consent and deletion, by KVKK and GDPR design principles
Three legal documents, two languages, versioned; consent is recorded against the exact version. Account deletion with a 30-day grace period; the account is closed and no longer served.
Roadmap
Planned; not claimed on this page today.
The hook points are in the code. When one of these enters the product the page will say so, and not before.
Glossary suggestions
RoadmapProposing service, sector and topic terms from a free-text bio and company description, for approval.
Pre-meeting brief
RoadmapA one-page 'why you should meet' summary from both sides' profile and company details.
Duplicate company rationale
RoadmapA 'why these two may be the same company' explanation on the merge screen.
Support reply draft
RoadmapA reply draft for the admin from the FAQ and the legal texts.
Report commentary
RoadmapA written summary on top of the six Excel reports.
CRM and LinkedIn
RoadmapCRM integration, LinkedIn import, a sponsor area, post-meeting notes.
How you get it
Six steps from discovery to operations support.
The on-prem model: branded for your organisation, installed on your server, published on the stores under your name, operated by Internative.
Discovery
Groups, the member model, the event calendar and the glossary needs are mapped together.
Branding
The vector logo goes in, 9 marks are generated, the palette is derived, the product name and copy become yours.
Installation
A single script onto your server; storage, email, push and the bot check connected on your keys.
Glossary and groups
The 163-term starter glossary curated for your sector; the first groups and lists uploaded.
Store release
The app is published on the organisation's Apple and Google accounts; the review account is ready.
Operations support
Releases, backups and updates are operated by Internative.
Price and timeline by proposal, based on member count; the discovery call is free.
FAQ
Frequently asked questions
No. One install per organisation; there is no tenant concept. Code and data stay with you.
With a six-digit code sent by email; there is no password. The code is valid for 10 minutes, with 5 attempts and a 60-second resend interval.
No. The only way in is an email address an admin added to a list; an uninvited address sees a calm explanation screen.
Five signals with fixed weights: offers what you seek (4), seeks what you offer (3), shared collaboration interest (2), shared topic (2), shared interest (1). The screen shows the reason, not a percentage. There is no learning model.
The organiser writes the schedule: sessions, slot length, breaks, tables. An off-grid time is rejected; two accepted meetings at the same table at the same time are impossible by the database index.
From the panel: daily or weekly, time and retention (1 to 90 days); a full archive goes to your own bucket, and a report email reaches the admins on every run. Restore is done with the standard tool by someone with server access.
Yes. Every admin write in the audit log with a before/after diff for 2 years; every outgoing email in the delivery ledger for 1 year, without the body.
Yes. A 30-day grace period: hidden from everyone at once, closed on day 30, cancellable in the app in between.
Yes. Logo, palette, product name and store identity are set up once for the organisation; the app is published on the organisation's own Apple and Google accounts.
Let us plan an install for your organisation.
We map your groups, member model and event calendar together; the demo runs on an example close to your organisation. The discovery call is free.
Internative: since 2017, 100+ enterprise clients, 400+ projects.
Request a demo
Tell us your organisation, member count and target event date; we will come back with the install scope.