# Vacanta: a posting-first job board operators own and run

> A job board looks like a feed, but the feed is the last visible stage of the system. Before a vacancy can be searched, it has to belong to an employer, carry terms a candidate can understand, pass a publication decision, remain current, and leave the public surface when it expires.

Source: https://saascode.ai/inside/vacanta-posting-first-job-board-operators-own-and-run · Published: 2026-08-26 · Section: builds · Product: Vacanta (https://saascode.ai/products/vacanta)

---
A job board looks like a feed, but the feed is the last visible stage of the system. Before a vacancy can be searched, it has to belong to an employer, carry terms a candidate can understand, pass a publication decision, remain current, and leave the public surface when it expires. Vacanta was shaped around that less visible lifecycle.

The result is a job-board SaaS delivered as source to the person who will operate it. Employer companies and candidates are users of that operator's service. They are not the buyer of the code, and treating them as if they were would have changed almost every product decision.

## Starting point

The useful starting point was the publication contract. Employers need a place to create vacancies and receive applications, but a board cannot let every draft become public by default. Candidates need a feed they can trust, yet trust is difficult to recover after stale or incomplete jobs have circulated. The operator needs to make the decision between those two sides without becoming an invisible superuser who bypasses the workflow.

Vacanta therefore centers a moderated path. An employer company prepares a vacancy and submits it for review. Publication follows an operator decision. Salary, workplace mode, and expiry are visible on the public record, so candidates can assess basic conditions before applying. That design makes moderation part of the product's operating model rather than a policy document written after launch.

It also establishes the product's economic level. The operator controls what employer companies pay to publish and keeps the relationship with those companies. A plan inside Vacanta describes the operator's offer to an employer; it is not a restriction placed by SaaSCode on the buyer. That distinction sounds grammatical, but it separates a platform business from a tool used to post one company's jobs.

## Reading the market

The job-board software market offers several clear routes. Niceboard and JobBoard.io emphasize a managed launch: hosting, administration, imports, backfill, and commercial tooling are handled inside the vendor's platform. JBoard and Job Boardly extend that hosted model with different combinations of scraping, aggregation, candidate tools, and integrations. WP Job Manager starts from the opposite direction, using an open WordPress plugin and an ecosystem of add-ons.

Those products reveal that “launch a job board” is not one request. Some operators want to connect a domain and avoid infrastructure entirely. Others want a familiar CMS. Another group wants the board itself to be an owned software asset, because its moderation policy, commercial model, and future workflows are part of the business. Vacanta addresses that last group.

The comparison also exposed what source ownership cannot excuse. Owning the code does not create an employer network, a candidate audience, or a supply of current listings. Managed competitors often include backfill, scrapers, integrations, and service teams precisely because the empty-board problem is operational as much as technical. Vacanta does not erase that work. It gives the operator a controlled platform on which to do it.

## The decisions that shaped it

The first decision was to make review precede publication. A board can optimize posting speed later, but it cannot retroactively prevent an unreviewed listing from damaging trust. The moderation queue gives the operator a clear place to approve, request changes, or reject. Employers still control their own vacancy work; the operator controls the moment it becomes part of the public market.

The second was to keep the employer and candidate experiences separate without breaking the lifecycle between them. Employer companies manage their vacancies and work with applicants in a private pipeline. Candidates maintain an editable profile, apply, and track their own outcomes. The same application connects those two views, but neither side receives the other's operating authority.

The third was to make the public listing explicit. Salary, workplace mode, and expiry are not secondary decoration. They influence whether a candidate can evaluate a role and whether a crawler can understand that the vacancy is still valid. Google documents the same discipline for `JobPosting` structured data: the markup belongs on the specific page for one job, and expired postings must be handled accurately. Vacanta's v1 distribution follows that narrow, verifiable path with job-page JSON-LD and a dedicated job sitemap. See [Google Search Central's job-posting guidance](https://developers.google.com/search/docs/appearance/structured-data/job-posting).

The fourth was to keep the operator's commercial controls at the operator level. Pricing, moderation, newsletters, and distribution health span employer companies, so they cannot be hidden inside one employer account. The buyer is running a market with multiple participants. The product has to let that buyer govern the whole board while keeping employer and candidate records in their proper contexts.

The fifth was to treat disabled capability as a product state, not a marketing opportunity. Semantic and vector matching have schema and a feature flag, but they ship disabled. That means Vacanta cannot be described as an AI matching engine. A complete applicant-tracking system is also outside the boundary: the private employer pipeline supports the board's application lifecycle, but it does not become a full recruiting suite by implication.

## What fought back

Distribution was the clearest place where an attractive claim could outrun evidence. Large boards and aggregators have admission rules, feed contracts, and changing policies. A technical adapter is not the same as an accepted channel. Vacanta has no proven v1 admission path to Indeed or Jooble, so neither is presented as shipped. The product commits to the surface it can demonstrate: canonical job pages with Google `JobPosting` data and a job sitemap.

That restraint creates an honest launch problem. A new operator still needs employers, current listings, and a repeatable way to keep the board useful. Hosted platforms can be the better choice when their backfill, scraper, import, and support systems are the decisive requirement. Vacanta asks the operator to solve supply and distribution deliberately instead of implying that source code includes a ready-made market.

The applicant boundary required similar care. A job board needs enough workflow for employers to receive and progress applications, and enough visibility for candidates to understand their outcomes. It does not automatically need every feature of an enterprise ATS. Calling the smaller lifecycle “complete applicant tracking” would make the product sound broader while making the description less accurate. The shipped boundary is more useful because it tells a future owner where extension work would begin.

Ownership itself is another tradeoff. A managed platform carries hosting, upgrades, and much of the operational support. Source custody transfers control, but it also transfers maintenance. The buyer must deploy, monitor, secure, and evolve the service. That is not a defect hidden behind the phrase “full source code”; it is the practical meaning of operating software as an asset.

## What shipped

Vacanta ships as a posting-first, multi-tenant job-board SaaS for an operator to deploy under their own brand. Employer companies can manage vacancies and work with applicants in private pipelines. Candidates can keep profiles, apply, and follow their outcomes. Public vacancies expose the terms that matter before an application, and every listing passes through moderation before publication.

The operator receives the broader control plane: employer pricing, moderation, newsletters, and distribution health across the board. Google-ready job pages and a job sitemap provide the verified distribution foundation. The product remains explicit about what is absent: semantic matching is disabled, complete ATS depth is outside scope, and unproven external syndication is not presented as a feature.

That scope makes the source a starting asset rather than a claim of market completeness. Vacanta supplies the controlled lifecycle on which a niche board can operate. The buyer supplies the market judgment, audience, employer relationships, infrastructure, and future changes that make the board distinct.

## See it

[See Vacanta →](https://vacanta.saascode.ai)

## Related reading

- [Job board software in 2026: choose by the changes you need to make](https://saascode.ai/inside/job-board-software-2026-change-rights-hosted-source-code.md)
- [Vacanta vs Niceboard: managed speed, source ownership, and a custom build](https://saascode.ai/inside/vacanta-vs-niceboard-source-ownership-custom-build.md)