32 Hours to Build a Rental Platform: The Apartspace Case

Thirty-two hours, with a business workflow behind the interface

Apartspace connects guests looking for a place to stay with the people running rental properties. A host needs to manage a portfolio, set rates, control availability, confirm bookings, keep guest records, and understand the finances. A guest needs a usable path from a request to a priced stay. Solomiia, the AI concierge, gives that journey a conversational entry point.

Developer Taras Hanych reports that Apartspace's initial implementation took 32 hours. Its repository records substantial early milestones across July 9–11, 2026: identity and roles, properties and rates, calendar and bookings, notifications, finance and analytics, then further marketplace and integration workflows. The code gives us a way to examine the substance behind the time claim.

Apartspace started from Semitexa Ultimate and reused prepared interface designs. Those are useful starting assets. The demanding work is connecting them to prices, permissions, persistence, and operations that behave consistently. That is where this case makes the strongest argument for Semitexa.

Follow one booking through the product

Start with a guest asking for an apartment for particular dates. The application must identify a real listing, check the proposed stay, and produce a quote from the host's rate plan. A weekly stay may have a different pricing mode from a short visit. A duration discount may apply. A deposit must be shown separately from rent.

When the guest requests the stay, the server checks the listing, dates, and contact details and obtains the price from the rate service. The owner's booking workflow decides whether the request can move to confirmation. Occupancy writes pass through the calendar's transactional conflict check. A confirmed booking then produces a domain event that the notification layer uses to send account managers an actionable update.

That journey crosses the guest interface, AI tools, pricing, booking, calendar, account ownership, and notifications. Each stage has a reason to exist, and each must agree with the others. Apartspace makes this connected workflow the unit of development. Semitexa provides the application structure in which those stages can be implemented and joined.

Apartspace exposes the difficult parts of a rental product

Apartspace connects a guest-facing rental experience with an owner's operational workspace. Its application includes identity and account roles, a property portfolio, rate plans, a calendar, bookings, guest records, finances, and notifications. The guest can talk to Solomiia, an AI concierge; the application maintains the structured data and rules behind that conversation.

The strongest evidence sits where a rental business can lose money or trust:

• A price has one calculation path. The quote calculator uses money in minor units, checks minimum and maximum stays, selects nightly, weekly, or monthly pricing, applies seasonal overrides in nightly mode, and chooses the largest applicable duration discount. It keeps the deposit separate from rent.
• Dates have precise boundaries. Availability uses half-open intervals: one guest may check out on the day another checks in. The occupancy write path includes a transactional locking conflict check. Booking writes handle specific database deadlocks and lock timeouts with a bounded retry; the locking design depends on the documented database isolation level.
• A booking has a lifecycle. The state machine permits defined moves from request to confirmation, check-in, check-out, and closure, with cancellation and refusal paths. Invalid jumps are rejected. Status history and domain events connect the transition to the surrounding application.
• The owner receives an actionable update. A confirmation listener finds the booking within its account, prepares the dates and amount, and directs account managers to the CRM record. A deduplication key accompanies the notification.
• AI operates through application rules. Booking parameters are checked on the server for an existing listing, valid future dates, a name, and a plausible contact number. The tool execution path obtains authoritative pricing from application services rather than accepting a model-supplied price.

These details make the delivery story substantial. The project has calculations, state transitions, ownership checks, failure handling, and interactions across modules. During this article's source review, the current tests covering quote calculation, booking transitions, interval overlap, deadlock retry behavior, and booking parameter validation passed: 48 tests, 134 assertions. That result supports those specific rules; database concurrency and complete user journeys require their own checks.

The 32-hour account has a concrete implementation record

Apartspace's early Git history makes the progression inspectable. The dates below identify recorded implementation milestones in the local repository, using its UTC+03:00 timestamps.

The first scaffold was recorded on July 9 at 13:09. By July 10 at 14:44, the repository contained a production deployment configuration alongside the earlier booking, calendar, finance, and analytics milestones. The 32-hour figure is the developer's reported implementation time; the dated commits supply a complementary record of what was being built. Calendar timestamps alone cannot measure that effort or certify a production release.

Apartspace continued to gain capabilities and hardening after this initial window. The current source review below examines the rules that exist today; the dated milestones above describe the early implementation. The distinction keeps the case useful: a substantial first product in a reported 32 hours, followed by continued development on the same foundation.

Semitexa moves the starting line forward

Apartspace draws on Semitexa's core runtime, authentication and access modules, ORM, SSR, media, LLM integration, and the Platform interface stack. Events and scheduling provide paths for the work surrounding its domain modules. These capabilities give the project a consistent place for each part of the booking journey.

The project still has to define the rate rules, availability semantics, booking states, and account ownership that make a rental business work. Semitexa gives those rules established paths to persistent data, rendered interfaces, events, and background jobs. More of the implementation window can go into joining the actual business workflow.

This is the engineering case for Semitexa's speed: Apartspace combines serious domain rules with reusable application infrastructure, and its implementation record shows how quickly that combination took shape. Prepared designs, focused scope, and development tools contributed too. The reported 32 hours is a real project's delivery account; the architecture explains a practical route to achieving it.

For a buyer, the useful challenge is concrete: ask a team to show the customer journey, the staff workflow, the rules that can reject an invalid operation, and the path to the next release. Semitexa has real projects in which those answers are visible.

A smaller second case: a museum in 16 hours

The Chernivtsi Regional Museum provides a second example in a different domain. Its developer reports a 16-hour initial implementation on an existing Semitexa installation, importing legacy content. The first museum commit includes page and event management, contact management, public templates, and resumable LLM translation tooling.

The museum also belongs to an application configured for five tenant module sets. Domain resolution selects its tenant context and module-scoped routes. Later work added a content map, web-console editing, and tenant-scoped translation synchronization. The current automatic update translator handles titles, descriptions, and eligible bodies; bodies above 12,000 bytes keep their existing English content.

This case broadens the evidence: the same foundation supports a multilingual institutional site as well as a rental product. Apartspace remains the central demonstration of connected business complexity and compressed implementation time.

Inspect the result, then inspect the mechanism

Open Apartspace to inspect the concierge and rental experience. The museum's English site provides the supporting institutional example. The administrative and business-rule evidence in this article comes from a review of their local source checkouts on September 30, 2026; public pages alone cannot demonstrate those internal capabilities.

Explore the foundation in the Framework Demo, or read how a request becomes a Semitexa page and why tenant context must travel with background work. Then bring a difficult workflow of your own. These projects show why a short implementation window can still contain serious application engineering.