Legal nameVIVAN LABS LTD
Company number17061582
RegisterEngland and Wales
EntityPrivate limited company, active
VIVAN LABS LTD engineers the layer between source systems and analysis: extraction, landing, modelling, contracts, tests, orchestration, lineage, access control and cost. Every claim below is either a fact on the public register or a commitment we will put into a contract, and each one is marked as which. Nothing on this page needs you to take our word for it.
This is what the register says. If any line here disagrees with the register, the register is correct and this page is out of date, so please tell us.
| Field | Value on the register |
|---|---|
| Registered company name | VIVAN LABS LTD |
| Company number | 17061582 |
| Company type | Private limited company |
| Company status | Active |
| Registered in | England and Wales |
| Nature of business (SIC) | 62012 business and domestic software development; 62020 information technology consultancy activities; 62090 other information technology service activities; 63110 data processing, hosting and related activities |
| Officers and persons with significant control | Published on the public Companies House register against company number 17061582. We do not reproduce personal details of individuals on this website. |
Why we print this. A UK limited company is legally required to disclose its registered name, number, place of registration and registered office. Most sites bury it in six point type at the bottom. Printing it as a legible table seemed better, because the register is the single description of this company that stands up whether or not you believe anything else here.
The phrase gets used for four or five different jobs. Here is the one we do, so that nobody buys the wrong thing.
We do this
Extraction, landing, modelling, testing, scheduling, lineage, access control and cost. The output is infrastructure and code in your repository plus documentation somebody else could pick up.
We do this
Taking a warehouse that grew organically and giving it ownership, contracts, tests and a lineage graph, without a rebuild. It is cheaper than starting again and far less risky, and it is the shape most of this work takes.
We do this
Classification, retention that actually deletes, deletion that propagates to downstream copies and backups, access reviews, and the technical evidence a data protection officer needs when the ICO asks a question.
Not this
We will make sure the numbers underneath your dashboards are right and traceable. Visual design, metric strategy and the reporting rollout need a different supplier, and being told that in the first reply is more useful to you than being sold the work.
Not this
We build the feature stores, training data pipelines and reproducibility around models. We do not build the models. A supplier who claims both is usually stretching.
Not this
We are not a contractor supply business. Work is scoped, priced and delivered against a written outcome, or we decline it.
The question worth asking a supplier is not who else have you done this for. It is show me how you would fail, and what happens to me when you do.
Ask us what happens if the engagement stalls, if a key person becomes unavailable, or if the company ceases to trade partway through a piece of work. The answers are the same ones we put in our terms: your code stays in your repository, your credentials are scoped and revocable, and nothing critical to your platform runs on infrastructure we control.
These are structural decisions, taken deliberately and kept to. They are the reason we can make the commitments set out on this site.
C1
We do not operate a SaaS component that a client platform depends on. Everything we build runs in the client's own cloud account, under the client's own billing and identity. That removes an entire category of supplier risk, and it is why an engagement can end without leaving anything of ours in your delivery path.
C2
The company is registered in England and Wales, contracts under the law of England and Wales, and defaults to UK or EU cloud regions for anything it touches. Where a client's chosen tooling forces a transfer outside the UK, we say so before the work starts and handle it under the IDTA or the UK Addendum rather than after the fact.
C3
The first engagement with any client is fixed scope and fixed fee. Retainers, if they happen at all, come after both sides have seen how the other works. This is slower and less profitable than the alternative and it is the arrangement we would want if the positions were reversed.
C4
Scopes, findings, estimates, risks and bad news go in writing before they are discussed on a call. A written record is what protects a client from a supplier's memory, and it is the only way an engagement can be handed to someone else halfway through without loss.
Points that come up often enough in a first conversation to be worth putting in writing here.
General enquiries get general answers. One specific figure gets a considered technical reply that follows it back to the row it came from, usually within two working days, and it costs you nothing to find out how we reason about a real platform before you commit to anything.