Skip to main content
Lampas HumanityGlobal Public Technology Initiative
Lampas HumanityGlobal Public Technology Initiative

Technology should empower humanity. Progress should benefit everyone.

Technology

Powerful tools, honestly assessed.

Technology can expand opportunity and accountability — or concentrate power and cause harm. Which of these happens depends on how it is designed, governed and used.

Our technological philosophy

Four convictions.

  • 01

    Technology is a means, not an end

    We start from a public problem and the people affected by it, then ask which technology — if any — genuinely helps. A tool that does not improve people's lives is not progress.
  • 02

    No technology is neutral

    Every system embeds choices about who benefits, who decides and who bears the risk. Those choices should be made openly and be open to challenge.
  • 03

    Public infrastructure deserves public scrutiny

    Systems that serve the public should be inspectable, auditable and governed in the public interest, with independent review before and after deployment.
  • 04

    Simplicity is a safeguard

    The simplest technology that solves the problem is usually the most affordable, the most secure and the easiest for others to maintain and own.

Areas of focus

What each technology can — and cannot — do.

For every area, we set out its potential public-interest contribution alongside its limitations and the safeguards it would require.

01

Artificial intelligence

Public-interest contribution
Assisting analysis of large datasets, translation across languages, access to information and more efficient, responsive public services.
Limits and risks
AI systems can be inaccurate, biased or opaque, and may reproduce existing inequalities at scale. They are not a substitute for human judgement on consequential decisions.
Required safeguards
Human review of consequential decisions, independent evaluation in local contexts, documentation of limitations and clear routes to challenge outcomes.

02

Open-source technologies

Public-interest contribution
Allowing public institutions and communities to inspect, adapt and own the tools they rely on, and avoiding dependence on any single provider.
Limits and risks
Open source still requires sustained maintenance, security review and skilled people. Publishing code is not the same as supporting it.
Required safeguards
Funded maintenance plans, regular security audits, and clear governance and contribution policies for every project.

03

Digital public infrastructure

Public-interest contribution
Shared, interoperable building blocks — such as identity, payments and data exchange — on which many public and private services can be built.
Limits and risks
Poorly governed infrastructure can exclude people or enable surveillance, and failures affect everyone who depends on it.
Required safeguards
Rights-based design, inclusive non-digital alternatives, legal safeguards and independent oversight of operation.

04

Blockchain, where appropriate

Public-interest contribution
Tamper-evident shared records can help where several parties that do not fully trust one another need a common, verifiable history.
Limits and risks
Most problems do not need a blockchain. It can add cost, complexity and energy use, and it cannot guarantee that the information entered is true.
Required safeguards
Used only after comparison with conventional databases; energy-efficient designs; never as a speculative token or investment product.

05

Secure data systems

Public-interest contribution
Storing and sharing sensitive information safely, enabling research and services without exposing individuals.
Limits and risks
No system is perfectly secure, and large concentrations of personal data become attractive targets.
Required safeguards
Data minimisation, encryption, strict access controls, privacy-preserving techniques and tested breach-response plans.

06

Financial technology

Public-interest contribution
Lower-cost payments, transparent transfers and access to financial services for people underserved by traditional institutions.
Limits and risks
Financial tools can facilitate fraud, over-indebtedness and exploitation if poorly designed or regulated.
Required safeguards
Operation only through licensed partners, compliance with financial regulation, consumer protection and clear disclosure of costs and risks.

07

Data analytics

Public-interest contribution
Turning raw data into insight for decision-makers, researchers and the public, and making evidence easier to use.
Limits and risks
Analysis is only as good as the underlying data, and numbers presented without context can mislead.
Required safeguards
Published methods, uncertainty stated plainly, peer review, and public correction policies.

08

Cybersecurity

Public-interest contribution
Protecting people, institutions and infrastructure from attacks that disrupt services and cause real harm.
Limits and risks
Threats evolve constantly; security requires ongoing investment rather than one-time fixes.
Required safeguards
Security by design, independent penetration testing, responsible-disclosure programmes and rehearsed incident response.

09

Interoperability

Public-interest contribution
Allowing systems built by different organisations to work together, so that data and services are not trapped in silos.
Limits and risks
Standards take time to agree, must be maintained, and can be undermined by proprietary extensions.
Required safeguards
Adopting established open standards wherever they exist, and contributing improvements back openly.

10

Distributed infrastructure

Public-interest contribution
Spreading computing, storage and connectivity across locations and operators to improve resilience, reduce cost and bring capacity closer to users.
Limits and risks
Distributed systems are harder to coordinate, secure and govern.
Required safeguards
Clear operating standards, continuous monitoring and shared, documented accountability among operators.

No magical solutions

When blockchain is the wrong tool.

Distributed ledgers and artificial intelligence are often presented as answers in search of problems. We would use them only where they clearly outperform simpler alternatives.

A blockchain is usually the wrong choice when…

  • A single trusted organisation already maintains the record.
  • Information must be correctable or deletable — for example, personal data covered by privacy law.
  • Speed, low cost and low energy use are essential.
  • The real problem is the accuracy of the information entering the system.
  • A conventional database with audit logs would do the job.

Lampas Humanity does not issue, promote or plan any cryptocurrency or token.

Before we build

Five questions asked of every technology choice.

  1. Question 1: Does it solve a real problem for real people?

  2. Question 2: Is there a simpler, cheaper or more proven alternative?

  3. Question 3: Who controls it, and who could be harmed by it?

  4. Question 4: Can it be maintained, audited and owned locally?

  5. Question 5: How will we know if it is not working?

Development principles

How we intend to build.

These principles would apply to every tool developed under Lampas Humanity.
  • Open by default

    Open-source code, open standards and open data wherever this is safe and lawful, so that work can be inspected, reused and improved by others.
  • Privacy and security by design

    Protection of people and their information is designed in from the first line of code, not added after harm has occurred.
  • Interoperable, not proprietary

    Building on shared standards and integrating with existing public systems, so that no institution or community becomes locked in.
  • Human oversight

    Technology informs decisions; accountable people make them. Consequential decisions always remain open to human review and challenge.
  • Evidence before scale

    Every tool is piloted, independently evaluated and openly reported on before it is expanded — including when results are disappointing.
  • Appropriate technology

    Choosing the simplest technology that works, designed for low bandwidth, low cost, local languages and the realities of the people it serves.

Technical collaboration

Build public-interest technology with us.

Engineers, security specialists, designers and researchers can help shape the technical foundations.