Related hosting
Somewhere sensible for processed work to live.
Hosting here means the arrangements around a processing job: where inputs land, where outputs wait, how long runs are kept and where the routine itself sits.
Scoped to the job. Provider named up front.
Four places a job touches
Where incoming files arrive. Kept separate from everything else, so nothing half-received is processed. Files are cleared once a run has completed and been checked.
Where processing happens. Temporary by design: working copies are removed at the end of each run.
Where finished outputs and run notes wait to be collected. Access is limited to the people you name.
Earlier outputs and notes kept for comparison, for a retention period you choose. When it lapses, they are deleted and the deletion is recorded.
Questions we answer before hosting anything
- Which provider and which country is the hosting in?
- Who, by name or role, can access each area?
- How are files moved in and out?
- How long is each kind of file kept?
- What happens to everything if the arrangement ends?
You get the answers in writing as part of the job specification. If an answer would be "it depends", we settle it before data moves.
What we will not claim
We do not claim to own data centres, to provide uninterrupted availability, or to watch systems overnight. Related hosting at FCR is a practical arrangement for processing work, delivered on infrastructure from an established provider that we identify to you by name.
If your needs are primarily about high-availability infrastructure, a specialist hosting company is the right first call, and we will tell you so.
Retention schedule illustrative
- Inbound filesUntil run checked
- Working copiesEnd of run
- Outputs awaiting collection14 days
- Run archiveAgreed per job
Periods shown are examples. Yours are set in the specification.
Hosting the routine itself
The rules that drive a processing job are as important as the data. We keep each job's specification, mapping tables and processing configuration together, versioned, so that the run in March uses exactly what was agreed in March.
If you later want to take the job in-house, you receive the specification and mapping in readable form. Nothing about the routine depends on knowledge held only in someone's head.
Need outputs held somewhere specific?
Tell us where they must end up and who needs them. We will propose an arrangement and explain its limits.