Skip to content

PCYBOX Lab

Your idea, checked before it is built.

The Lab turns an uncertain idea into a decision, then into a product, in fixed-scope steps. At each step: a stated duration, a precise deliverable, and the choice to continue or stop.

PCYBOX Lab
See the packagesTell us your idea

The problem

A promising idea, but too many unknowns to sign.

Feasibility is unproven

Nobody can yet say whether the solution can be built, with which technologies, or at what cost.

The budget must be justified

Management, a committee or a funder expects concrete evidence before committing to a full project.

Security often comes too late

Added afterwards, it is expensive. We design it in from scoping, at every step.

Packages

Three packages, each with a fixed scope.

Each package can be ordered on its own, with a deliverable defined upfront. You are never committed to the next one. We run a limited number of projects in parallel, to keep to the stated timelines.

Package 1

Feasibility study

Indicative duration : About 2 weeks

When to choose it
You have an idea or a problem, but you do not yet know whether it can be done, or how. Useful before a budget, a tender or a funding request.
Deliverable
A technical memo: compared options, identified risks, effort estimate and a reasoned recommendation.
Decision at the end
Launch a prototype, or stop with a documented decision.
Price
Quote-based, fixed scope
Scope details

Included

  • Scoping workshops with your teams
  • Review of technical options, including existing solutions
  • Risk identification, including security risks
  • Effort estimate for the next steps

Not included

  • Production code
  • Testing on your live systems

What you provide

  • A contact person available during the study
  • Known documents and constraints: business, regulatory, technical
Request a study

Package 2

Working prototype

Indicative duration : About 4 to 6 weeks

When to choose it
Feasibility is established. Now you need to show the solution works, to decision-makers, users or a funder.
Deliverable
A working demo of the main user journey, with source code and documentation.
Decision at the end
Move to the MVP, adjust the prototype, or stop.
Price
Quote-based, fixed scope
Scope details

Included

  • Working demo of the priority user journey
  • Test or anonymised data
  • Documented architecture choices
  • Demo session with your teams

Not included

  • Production deployment and operations
  • Coverage of every use case
  • Full integration with your systems

What you provide

  • The priority journey to demonstrate
  • Users available to give feedback
  • Test data, if needed
Request a prototype

Package 3

Secure MVP

Indicative duration : About 2 to 3 months

When to choose it
The prototype convinced. You want a first product that real users can use, within a defined scope.
Deliverable
A usable product, with source code, automated tests, the security review report and documentation.
Decision at the end
Go to production, or continue with our Secure development service.
Price
Quote-based, fixed scope
Scope details

Included

  • Usable product within a defined functional scope
  • Security designed in from the architecture: threat modeling, code review
  • Automated tests and a security review before delivery
  • Knowledge transfer to your team

Not included

  • Changes outside the defined scope
  • Long-term operations and maintenance, available through the Secure development service

What you provide

  • A product owner on your side
  • A hosting environment, or your approval of the one we propose
  • The access required, framed in writing
Request an MVP

Lab or Secure development?

The Lab helps you decide. Secure development builds what has been decided.

If you do not yet know whether or how your idea can work, choose the Lab. If you know precisely what needs to be built, choose Secure development.

PCYBOX Lab

  • High uncertainty about feasibility or the solution
  • Short, fixed-scope steps with a decision point
  • Deliverable: evidence, then a first product

Secure development

  • Known, specified need
  • Full project, over time
  • Deliverable: a platform in production, maintained
See the Secure development service

Method

Four stages, in every package.

  1. Stage 1

    Scope

    Goals, users, constraints and the expected deliverable, agreed in writing before we start.

  2. Stage 2

    Explore and build

    Options are tested and the solution is built, with regular check-ins with you.

  3. Stage 3

    Verify

    Testing and a security review suited to the step: security is designed in from scoping, not added at the end.

  4. Stage 4

    Decide

    You receive the deliverable with a clear recommendation: continue, adjust or stop.

No security testing is carried out on your systems without your written authorization.

Evidence

What the Lab has already built.

Two products designed by the PCYBOX Lab for our own needs, then released as open source. They are not client projects.

Network visibility for workstations

Orbis

How we built OrbisOrbis fact sheet
Problem
Knowing which application on a computer talks to which server, in real time, without a specialist tool or a heavy enterprise solution.
Approach
A local tool that links each connection to the process behind it, shown as a graph and a world map. History stays on the machine. Alert thresholds are explicit, to avoid false alarms. Released as open source to be tested by real users.
Result
Orbis Community, open source (AGPL v3): over 190 stars and 25 forks on GitHub, and demos that reached more than 187,000 people. User feedback defined the scope of Orbis Enterprise, now in preparation.

Attack path simulation

AttackGraph

AttackGraph fact sheetSource code on GitHub
Problem
Explaining how an attack spreads through an infrastructure, and testing a defense, without touching a real system.
Approach
A lab that runs entirely in the browser: you build a simulated infrastructure, watch an attack move from one element to the next, and check whether the chosen measures stop it.
Result
An open source tool released on GitHub, used to explain a risk by example. Everything is simulated: no real system is attacked and no real data is used.

Frequently asked questions

What people ask us about the Lab.

Do I need a specification?

No. An idea, a hypothesis or a description of the problem is enough. Scoping, at the start of each package, sets the goals and the deliverable in writing.

What happens at the end of a package?

You receive the deliverable and a recommendation. You then decide freely: move to the next package, adjust, hand the next phase to our Secure development service or another team, or stop.

How much does a package cost?

Each package is quoted with a fixed scope after a first conversation. The price covers the defined deliverable: no open-ended time-based billing.

Who owns the code and documentation?

On custom projects, source code and documentation are handed over to you. Licensing and reuse of technical components are specified in the contract.

Does the Lab only work on cybersecurity?

No. The Lab also works on business platforms, internal tools, APIs and AI-powered solutions, always with security designed in.

Does our data stay under our control?

Yes. We prefer to work with test or anonymised data, and solutions can be designed for on-premise deployment. A non-disclosure agreement can be signed at scoping.

Do you work with clients outside Senegal?

Yes. The Lab is based in Dakar and works remotely or on site, in French and English, for organizations in other countries.

Not sure which package to choose?

Describe your idea or problem. We will tell you which package fits, or whether you should go straight to Secure development.

Tell us your ideacontact@pcybox.com