AstrolobeUnderstand the estate before the move starts.
Use the qualification when a migration or replatform is planned but the true structure, scope, or risk of the source estate is still unclear.
Astrolobe Estate Qualification
Know what you're dealing with before you commit the bigger budget.
Astrolobe gives engineering teams an evidence-backed read on a technical estate before a migration, rebuild, consolidation, or replatform. You receive the observations, provenance, limitations, and recommendation behind the decision — not a black-box verdict.
If we do not see a credible path to creating value materially above the cost of the engagement, we'll tell you before payment.
Who it's for
Technical founders, engineering leads, and small engineering teams facing an expensive decision about an estate they do not fully understand.
The decision it serves
Whether to migrate, rebuild, consolidate, clean up first, replatform, narrow the scope, or stop.
What $2,500 buys
A bound scope, a frozen-engine run where applicable, founder-led qualification, and evidence supporting the recommendation.
What arrives
A private report, source-traced evidence packet, limitations, recommendation, founder readout, and 14-day clarification window.
When this earns its fee
The qualification exists to improve a more expensive decision.
We are not selling a report for its own sake. The engagement should reduce discovery work, expose risk earlier, or make the next engineering commitment easier to defend.
Establish what the team actually inherited.
Use it when repositories, files, exports, documents, logs, packages, or legacy material have accumulated beyond reliable institutional memory.
Decide what deserves the next dollar.
Use it when the real question is whether to clean up, consolidate, rebuild, migrate, deepen the investigation, or stop investing in part of the estate.
What you receive
Eight deliverables. Nothing vague.
Every item below is produced for the founding qualification whether the technical result is positive, negative, mixed, or inconclusive.
The exact workload, environment, and question, agreed and fixed before work begins.
What was examined, what was observed, and what those observations mean for the decision.
The evidence supporting the findings, with provenance back to the material and run where the method supports it.
Identification, profiling, organization, reduction, retention, or rejection only where actually executed and evidenced.
What did not work, what could not be determined, and what remains uncertain. Stated plainly.
Proceed, narrow, clean up first, run a deeper evaluation, or stop — bound to the evidence produced.
A working session to walk the evidence, limitations, and recommendation directly with the person who performed the qualification.
In-scope questions about the delivered report and evidence, with acknowledgement targeted within two business days.
Scope & pricing
One fixed founding offer. Larger estates are scoped before payment.
A small but structurally difficult estate can require more work than a much larger coherent one, so file count and storage size alone do not determine price.
See example scopes & pricing Illustrative, not automatic quotes
$2,500 fixed
First three accepted external customers. One bounded estate, one primary decision question, limited source families, no custom production integration, and a five-business-day target after START_READY.
From $5,000
More heterogeneous material, additional source families, deeper qualification or reconciliation, or greater founder analysis than the founding scope can responsibly absorb.
$10,000–$25,000+
Multi-repository or multi-source estates with legacy exports, documents, logs, archives, conflicting structures, unclear provenance, or materially broader reconciliation work.
Get a quote
Broad organizational estates, unusual security or handling requirements, multiple systems, or custom scope. Some data classes and requirements may remain outside Astrolobe's current service boundary.
These are examples, not a calculator. Astrolobe confirms the exact workload, deliverables, delivery window, and fixed price before payment. Quote review does not authorize data transfer.
What changes the quote?
Price is driven primarily by the work required to produce a bounded, defensible qualification — not by a single size metric.
Source-family countStructural diversityReconciliation depthEvidence depthDecision complexityData-handling requirementsFounder delivery effortDelivery urgencyFile / record countStorage size
Purchase and delivery path
Fit first. Scope and price second. Payment third. Evidence after that.
No customer should discover the real scope after being charged. Qualification class, deliverables, delivery window, and fixed price are agreed before payment.
Describe the estate and the decision
Send the decision in front of you, a non-sensitive estate description, rough scale, major source families, timeline, and data class. Do not send source data during quote review.
Fit check and scope classification
Astrolobe decides whether the work appears useful and which scope class fits. If there is no credible path to value materially above the engagement cost, we say so here.
Execute the bounded order
The exact workload, decision question, deliverables, data boundary, delivery window, price, and terms are fixed in writing. Only then is the private Stripe payment route issued.
Run the frozen engine and founder-led qualification
Work begins at START_READY: executed order, cleared payment, accepted inputs, bound scope, and no unresolved rights, data, dependency, or scope HOLD. DRE is used only within qualified capability and the founder interprets the evidence.
Record what actually happened
What was identified, organized or reduced where applicable, retained or rejected where applicable, what failed, and what remains uncertain — without turning inference into fact.
Deliver the decision package
The founding class targets delivery within five business days after START_READY unless the executed order states another agreed window. Larger scopes receive their own delivery window before payment.
The evidence standard
You are not asked to trust a verdict. You get what produced it.
The frozen engine is bound to a pinned package identity. Public proof stays limited to what accepted evidence demonstrates.
Files represented in a real end-to-end structural estate inventory run.
Closed accounting in that reference run — every inventory record classified.
Independent replay produced an identical output hashlist.
Original source files were not mutated in the reference run.
| Property | What was verified on the accepted build |
|---|---|
| Determinism | Two independent runs over the same input produced an exact matching output hashlist. |
| Source preservation | Original files were not mutated. Source hashes were preserved and checked. |
| Closed accounting | Every inventory event was classified under the declared rule. Nothing silently disappeared. |
| Filter trace | The ordered list of filters applied is recorded and inspectable. |
| Failure-closed input | Duplicate IDs, missing IDs, and invalid numeric values were rejected rather than silently absorbed. |
| Interruption safety | An interrupted run preserved its sentinel; recovery proceeded on a fresh path without overwriting output. |
| Overwrite refusal | The engine refuses to write over an existing output location. |
The honest boundary on the 4,063-file reference run. It operated on a file-level inventory of a real estate; file contents were not opened and the retention rule was structural. The retained/rejected counts in that run demonstrate controlled structural classification, not semantic relevance, customer ROI, or a universal reduction rate. Content-level reduction is verified against known-answer fixtures at a smaller scale. Every customer report states what was actually executed on that customer's bound workload.
Boundaries
What this is not, so you can decide quickly.
Claims stay bound to the exact workload, environment, method, and evidence produced in the engagement.
A valid result may be negative
Positive, negative, mixed, and inconclusive are all completed qualifications. A technically honest negative — reported truthfully with its evidence — is the qualification working, not failing.
Not a production or outcome guarantee
- No guaranteed reduction percentage, throughput, savings, or ROI
- No production deployment or production-readiness guarantee
- No engine source or binary distribution
- No OEM, redistribution, sublicensing, exclusivity, or IP assignment
- No open-ended integration, monitoring, or on-call support
Start with the smallest lawful dataset
The founding class is limited to buyer-authorized non-sensitive project and file workloads under a bound transfer method, local processing, retention limits, and deletion or return on completion.
Regulated, high-risk, credential, or prohibited data is outside the founding boundary. A larger quote does not automatically make an otherwise prohibited data class acceptable.
Refund terms
Know the money terms before a charge.
For refund accounting, the $2,500 founding engagement is divided into two $1,250 service obligations: qualification work-start and final delivery.
Before substantive work
Written cancellation before substantive qualification work begins receives a full $2,500 refund.
Work begun, delivery pending
The $1,250 final-delivery obligation is refundable by default. The work-start portion is retained only to the extent substantive in-scope work was actually performed. If Astrolobe cannot perform the agreed qualification, you receive a full refund.
After proper final delivery
A negative, mixed, or inconclusive result is not by itself a refund trigger. Material scope omissions are handled first through correction or re-performance within the original scope. Non-waivable rights remain unaffected.
The method is citable. The implementation stays protected.
The Astrolobe Method — Foundations V1.1.1 is publicly available with DOI 10.5281/zenodo.21923828. Public doctrine does not transfer proprietary Data Reduction Engine implementation rights.
A founding engagement runs against a pinned, hash-verified package.
The accepted package identity does not shift mid-engagement. The report remains bound to the actual build, workload, method, and evidence used.
DRE V1.59.0 Phase 48 package SHA-256
A9E53E496787C3A4ADE49B5DF2B5B0FE7B3E7C7365A069336C57E959BCFEA977Get a quote
Tell us about the decision, not the confidential data.
Quote review only needs enough non-sensitive information to determine fit and scope class. Do not attach source files, credentials, regulated data, or confidential estate contents.
Useful details for a quote
- The decision you are trying to make
- General estate type: repos, files, docs, logs, exports, databases, archives, or mixed
- Approximate file/record count and storage size, if known
- Number of major repositories or source systems
- How long the estate has accumulated
- What makes the decision difficult today
- Your desired decision date or timeline
- Whether sensitive, regulated, credential, personal, health, financial, export-controlled, or other high-risk material is involved
Quote review does not authorize data transfer and does not guarantee that Astrolobe can accept the estate or data class.
One estate. One important decision. Start with fit.
For the $2,500 founding qualification, send the organization, decision question, non-sensitive workload summary, timeline, and data class. We scope first, agree the order and price second, and issue the private payment route only after that.
Seller: Astrolobe LLC · Founder-led contact: andrew@astrolobe.com · Sold formally as the Astrolobe Founding Qualification Pilot. This page is an offer summary, not a substitute for the executed buyer-specific order and terms.