Pricing

Pricing: quoted by scope, not a fixed bundle

Why local deployment is quoted by scope: hardware, current setup, migration and timing differ too much. Also covers the three modes, what changes a quote, payment and cancellation. No online payment yet.

Package Scope Price Delivery Details
Home AI lab deployment review A remote look at your hardware, system and services, with a written plan you can act on: what can run, what is stuck, what to change first. Review first, then a written plan Quote on request Remote build + docs Details

Built from the same catalog the site uses. A package that is not on sale never shows a stand-in price.

Why there is no fixed price

“Set up Traefik” can mean one extra entrance on a clean Docker host. It can also mean migrating a dozen services, replacing expired certificates, fixing DNS and adding backups on the way. A fixed price is a guess, and someone ends up paying for the guess: either the customer, or the scope quietly shrinks.

So the order is: agree the scope, then quote.

Three ways to work

Mode What you get Fits
Remote review one remote session + written advice on bottlenecks and next steps hardware or system fit still unclear
One-time build configuration, documentation, verification steps, follow-up in an agreed window the goal is clear and needs to run
Phased project phase plan, acceptance per phase, monitoring and backup integration several services or nodes, long-term maintenance

What changes the quote

  • Current environment: clean, half-built, or a migration from an old machine.
  • Number of services: one entrance and ten entrances are different jobs.
  • Network: public IP, Tunnel availability, Access requirements.
  • Data and backups: migration needs and usable backup media.
  • Timing: evenings, weekends, or a required downtime window.
  • Delivery depth: configuration only, or documentation, recording and follow-up.

Payment

  • There is no online payment yet, and no card details are collected.
  • Once scope is agreed, the quote covers the work, deliverables, timing, payment points and cancellation terms.
  • A common arrangement is a share before work starts and the balance on delivery; the quote is the reference.
  • Ask for an invoice or receipt when scope is agreed.

Cancellation and refunds

  • Not started: handled per the quote, usually a full cancellation.
  • Started but not delivered: settled for the work completed, the rest returned.
  • Delivered: you have the deliverables, so “I did not use it” is not a refund reason. If it does not match the agreed scope, it is fixed first; if it cannot be fixed, the quote applies.

Full terms: cancellation and refunds.

Not included

  • Hardware purchase and carrier changes.
  • Long-term on-call, 24/7 response, unlimited revisions.
  • Third-party services (Cloudflare, domains, object storage and similar).
  • Any guarantee of model performance, third-party availability or future compatibility.

Questions

Can I do the review first and decide about deployment later?

Yes. The review is a separate project with written advice; whether to continue is your decision.

What should I send before a quote?

Ideally the assessment text from the home page, your current system and service list, the goal, your timeline and whether downtime is possible. Specific beats vague.

Why not publish a price list?

Because the same service name can hide ten times the work. A fixed price makes both sides assume a scope, which is how disputes start.

Can I pay now?

No online payment. Scope is agreed by email, then the quote sets the payment method.

Next

No online checkout yet. Send your setup and goal by email. The reply says whether the scope fits; a written quote then covers the work, timing and payment. No card data is collected here.

Not sure where to start?

Run the assessment first, or send your setup and goal by email. The reply says whether it fits and what happens next.