nikom.workIndependent engineering studio

Directories / marketplacesWorking systems · public release and private control plane observed

A directory people can use and operators can survive.

A large directory needs a safe path from source intake to public release. The working foundations cover immutable public pages, route migration, fail-closed source adapters, duplicate review, bounded media work, moderation, search, and rollback.

51,098-page public release with 321,904 redirects · 4 controlled source adapters · separate 1,202,321-row migration rehearsal

Estimate your version
Approach
Adapted to your business
Hosting
Your server or cloud account
Starting range
$25k–$120k+
Support
Handoff or ongoing support
First useful outcome

A useful first release, built around the real job

A marketplace or directory fitted to the vertical, geography, listing model, moderation rules, monetization, and existing data.

  • Canonical listing and taxonomy model
  • Public listing and detail surfaces
  • Operator administration
  • Fail-closed import or manual listing workflow
  • Media storage and processing boundary
  • Deployment, backup, and handoff documentation
Working flow

How the system fits together

  1. Legacy data or controlled sources
  2. Duplicate and qualification review
  3. Bounded media processing
  4. Operator acceptance
  5. Validated immutable release
  6. Blue/green activation and rollback
Your implementation

Your version follows your business

The reusable parts give us a head start. Your version still follows your data, staff, approvals, integrations, and infrastructure—not somebody else’s generic process.

Already built

This is not a blank-slate proposal

One observed directory release contains 51,098 immutable pages, 409,495 classified route outcomes, and 321,904 redirects. Its newer private control plane implements four source adapters, durable duplicate decisions, bounded restart-safe media queues, private review and publishing routes, and default-off quota-bound publication that still passes the complete build and activation gate. Separate builds provide a reconciled 1.2-million-row migration rehearsal and established-marketplace replacement slices; those figures and capabilities are not presented as one product.

Wrong fit

When this is the wrong tool

  • An unvalidated marketplace idea with no supply, demand, or operating owner
  • A project without a lawful operating model, content policy, and named owner
  • Sensitive-market work without documented age, identity, consent, media-rights, moderation, takedown, and payment-provider rules
  • A cheap template expected to replace product management and marketplace operations
Related builds

The case studies show what shipped, what was tested, and what is still unfinished.

Property listing operations softwareA bounded industry workflow for listing intake, approval, media, status, publication, enquiries, and controlled migration. 51,000-page adult-services directory migrationImmutable Rust releases plus the newer private review and publishing control plane. Private intake before public releaseFail-closed adapters, durable duplicate decisions, bounded media, and a default-off publishing path. Established adult-services classifieds rebuildA separate public, account, advertiser-billing, media, search, and operator replacement. 1.2-million-row catalog migrationChecksum-evidenced import and reconciliation before cutover. Bilingual adult-services directoryConsent, moderation, private media, translation, and controlled publishing.
Project cost calculator

Build a first-pass budget

Start with the useful core, then add only the parts your version needs. The calculator updates here in your browser; nothing is submitted until you attach the estimate to an enquiry.

Useful core releaseThe included scope described above, adapted to one business and deployed into your account. $25k–$45k
Choose optional scope
Estimated one-time build $25k–$45k Useful core only
Core release
$25k–$45k
Optional scope
$0

Selected scope

  • Useful core release
Choose what happens after launch
Ongoing costHandoff — no ongoing fee
Assumptions behind this range
  • One person can approve scope and product decisions.
  • The source data is usable and available for review.
  • Deployment goes into infrastructure you control.
  • The reusable core remains mine; your data and business-specific work remain yours.

Messy data, migrations, unusual integrations, compressed deadlines, and deeper production responsibility can move the range.

Attach estimate and continue

This is a planning range, not a quote or a promise of delivery dates. I confirm scope, dependencies, and responsibility before proposing a build.

After launch

Run it yourself, or keep me around

I fix agreed-scope defects for 30 days after handoff. Then you can take over completely or keep me involved for maintenance, production help, or reserved development time.

Handoff

No ongoing fee

You take over the agreed release. I still fix build defects for 30 days; ongoing updates and operational help are separate.

Maintenance

$1.5k–$3k/month

Annual commitment. Scheduled releases, security and compatibility fixes, and planned upgrade help. No incident response or custom development.

Production support

$3.5k–$6.5k/month

Six-month minimum. Maintenance, one-business-day response on working days, deployment help, and a monthly allowance for incident or operational work.

Reserved engineering

$7.5k–$12k/month

Six-month minimum. Priority queue, planned release work, and reserved engineering capacity. Unused capacity does not roll over; larger features are scoped separately.

Ongoing maintenance, upgrades, and incident response are separate services.