Submission declined on 19 May 2026 by MSK (talk). This draft appears to contain text generated by a large language model (such as ChatGPT). You cannot use LLMs to generate article content. LLM-generated pages with certain obvious signs of being machine generated may be deleted without notice. Instead, only summarize in your own words a range of independent, reliable, published sources that discuss the subject. See the advice page on large language models for more information. This draft's references do not show that the subject meets Wikipedia's criteria for inclusion. The draft requires multiple published secondary sources that: provide significant coverage: discuss the subject in detail, not just brief mentions or routine announcements; are reliable: from reputable outlets with editorial oversight; are independent: not connected to the subject, such as interviews, press releases, the subject's own website, or sponsored content. Please add references that meet all three of these criteria. If none exist, the subject is not yet suitable for Wikipedia. If you would like to continue working on the submission, click on the "Edit" tab at the top of the window. If you have not resolved the issues listed above, your draft will be declined again and potentially deleted. If you need extra help, please ask us a question at the AfC Help Desk or get live help from experienced editors. Please do not remove reviewer comments or this notice until the submission is accepted. Where to get help If you need help editing or submitting your draft, please ask us a question at the AfC Help Desk or get live help from experienced editors. These venues are only for help with editing and the submission process, not to get reviews. If you need feedback on your draft, or if the review is taking a lot of time, you can try asking for help on the talk page of a relevant WikiProject. Some WikiProjects are more active than others so a speedy reply is not guaranteed. How to improve a draft Wikipedia:Contributing to Wikipedia – a basic overview on how to edit Wikipedia. Help:Wikitext – how to use the markup Help:Referencing for beginners – how to include references Wikipedia:Article development – how to develop your article Wikipedia:Writing better articles – how to improve your article Wikipedia:Verifiability – make sure your article includes reliable third-party sources You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Add tags to your draft Editor resources Easy tools: Citation bot (help) | Advanced: Fix bare URLs Declined by MSK 2 months ago. Last edited by MSK 2 months ago. Reviewer: Inform author. Resubmit Please note that if the issues are not fixed, the draft will be declined again.

• Comment: In accordance with Wikipedia's Conflict of interest guideline, I disclose that I have a conflict of interest regarding the subject of this article. ~2026-29736-66 (talk) 22:51, 17 May 2026 (UTC)

Coliving Express is a free and open-source web application for the operational management of coliving communities, developed by the Finnish entrepreneur Kalle Sintonen.^[1] First released in May 2026, it provides a single self-hosted system through which a coliving operator can run multiple properties — handling resident applications, property guides, shared bicycles and cars, sauna and meeting-room bookings, a shared physical-item inventory, a community wish-list, and a centralised ticket inbox — without dependence on a proprietary platform or third-party SaaS provider.^[1][2]

The software is written in PHP, distributed as a single ZIP archive with no external runtime dependencies, and licensed under the MIT License.^[3] It is intended as infrastructure for community-scale sharing economy arrangements.^[4]

As of 18 May 2026, the stable release is v1.2.0, a user-interface polish release.^[5] An interactive demonstration of the full role-based interface is hosted at the project website.^[1]

The project originated at Northern Seasons, a coliving community in Outokumpu, North Karelia, Finland, where the author sought an open-source alternative to proprietary property management systems.^[6] The first public release, v1.0.0, shipped on 14 May 2026 with six modules — applications, properties, bikes, rooms, inventory and a resident directory.^[5]

Successive minor releases broadened scope:

• v1.1.0 (16 May 2026) added shared cars, saunas, a wish-list module, property guides, and a centralised ticket inbox. The interface adopted Google Material Symbols throughout.^[5]
• v1.1.1 (17 May 2026) introduced an automatic database migrator, four built-in user-interface languages (English, Finnish, French, Spanish) and a built-in email notification system covering applications, tickets and reported vehicle issues.^[5]
• v1.2.0 (18 May 2026) is a UI polish release: a defined shadow system, refined pill badges, focus rings, and cleaner tables. No schema or behavioural changes.^[5]

The codebase is approximately 200 kilobytes when packaged and free of external runtime dependencies.^[3]

Coliving Express requires PHP 8.1 or later and either MySQL 5.7+ or MariaDB 10.3+.^[7] Its internal framework comprises approximately twenty PHP classes — a regular-expression router, a thin PDO wrapper, session-based authentication with per-session CSRF tokens, an auto-migrator, a translation layer, a small mail engine using PHP's built-in mail() function, and a module/theme manager.^[2] All HTML is rendered server-side from plain PHP templates; no JavaScript framework is required. A bundled installer wizard performs the initial environment check, database creation and schema execution.^[7]

A single installation hosts an arbitrary number of independent coliving organisations. Each organisation has its own selection of enabled modules, theme, branding, members and outgoing email address. Users hold one site-wide account that may carry different roles in different organisations, across four levels: super administrator (site-wide), coliving administrator (one organisation), moderator (day-to-day operations), and resident (bookings, wish-list, tickets).^[2]

An in-process migrator, introduced in v1.1.1, compares the package version (compiled into the front controller) with the installed_version stored in the database on every request. If the package version is newer, the migrator executes every applicable SQL file under database/migrations/<version>.sql in semantic-version order, using a short-lived advisory lock to prevent concurrent runs by multiple web workers.^[5] In practice, operators upgrade by replacing the source files alone.

Coliving Express v1.2.0 ships eleven modules, three of which are flagged "core" and always enabled:^[2]

Translation strings are stored as flat PHP associative arrays in app/Lang/<locale>.php. A global helper function performs key lookup with placeholder substitution. The resolution order for a request's locale is: explicit session selection, the signed-in user's preference, the active organisation's default, the site default, and finally the fallback locale (English). Missing translation keys fall back to English; missing English keys fall back to the key itself, so partially-translated locales remain functional.^[5]

The software includes a built-in email notification engine using PHP's built-in mail() function to send multipart text and HTML messages. Five built-in events trigger notifications: new application, application status change, new ticket, ticket comment (with separate handling for internal notes), and reported bike or car issue. Notifications are per-user opt-in (enabled by default), locale-aware, and per-organisation brandable through a custom from-address. Every send is recorded in a dedicated audit log for later review.^[5]

Four themes ship by default: Nordic (a light, institutional green inspired by Finnish public-sector design), Forest (deep emerald on cream), Sunset (terracotta and amber) and Midnight (dark mode). Additional themes can be added by dropping a CSS file into the themes folder; all themes share design tokens defined in the base Nordic file.^[3] Iconography uses Google Material Symbols.

Coliving Express is distributed under the MIT License as a single ZIP archive, with no requirement for Composer, Node.js or any front-end build step.^[3] The author has stated that the dependency-free packaging is a deliberate constraint intended to keep the software runnable on inexpensive shared hosting and approachable for developers unfamiliar with modern PHP tooling.^[4]

Commercial property management systems aimed at conventional rental housing typically charge per-unit fees and offer narrow support for the operational realities of coliving, where significant value is generated by shared resources beyond housing itself. Existing coliving-specific commercial software is distributed on a SaaS basis.^{[citation needed]}

The operational surface of a coliving community is broader than any single conventional product addresses. A typical European coliving operator manages, in addition to housing applications and tenancies, some combination of shared bicycles, shared vehicles, a sauna (in Nordic countries essentially universal), one or more co-working or meeting rooms, a shared kitchen and shared physical inventory, and a continuous flow of maintenance issues requiring triage. Operators that fail to coordinate these resources often default to ad-hoc tooling such as group messaging apps, spreadsheets and paper sign-up sheets — an approach that scales poorly and produces no operational record.^[1]

The sharing economy is an economic system in which assets, services or skills are shared between individuals — either for free or for a fee — typically with the support of internet-based coordination.^[8] Commonly cited large-scale examples include ride-hailing services (such as Uber and Lyft), short-term accommodation marketplaces (such as Airbnb), peer-to-peer lending and tool libraries.

A parallel strand — variously described as the commons-based sharing economy, platform cooperativism, or community-led sharing — emphasises locally-owned and locally-governed sharing arrangements rather than venture-backed marketplaces.^[9] Coliving sits in this second strand, along with bicycle libraries, tool libraries, neighbourhood carsharing and shared workshops or hackerspaces. Open-source, self-hosted software tailored to the multi-resource, multi-property reality of community-scale sharing has remained scarce.

Coliving Express is positioned as infrastructure for community-scale sharing, in a similar role to that played by WordPress for publishing or Mastodon for federated micro-blogging.^[1][4]

Design properties relevant to that role include:

• No central platform. Each installation is owned and operated by the community using it; there is no marketplace, no commission, and no central database operated by the software's author.
• Multi-resource by default. Bicycles, cars, sauna, rooms, inventory and tickets are bundled into one system, reducing the operational overhead of running multi-modal sharing.
• Resident-led inputs. The wish-list and ticket modules give residents structured, auditable channels to propose purchases and report problems.
• Low cost of entry. With no Composer or Node.js dependency and an approximately 200 KB footprint, the software runs on the cheapest tier of commodity shared hosting.
• Forkable and modifiable. The MIT licence permits commercial use, modification and redistribution, including sector-specific forks for cohousing, retirement communities, hackerspaces and intentional communities.
• Localised. Built-in support for four European languages lowers the language barrier for European operators.
• Auditable. Photo-gated bike PINs, mileage logs and a centralised ticket inbox produce a record of how shared resources are actually used and maintained.

The project is intended to make it easier for non-technical operators to start and run community-scale sharing economy ventures without the recurring software costs that can dominate the budgets of small operators, and without the data-extraction dynamics of large platform intermediaries.^[4]

• Coliving
• Cohousing
• Property management system
• Sharing economy
• Platform cooperative
• Commons-based peer production
• Free and open-source software
• Self-hosting (web services)
• Bicycle-sharing system
• Carsharing
• Tool library
• Northern Seasons

• Official website
• Features overview
• Requirements and installation
• Changelog
• Download (current stable release)
• Live interactive demo
• Kalle Sintonen — personal homepage
• Northern Seasons — the coliving community where the software was first deployed