Frequently asked questions
A few practical answers about working with BytecodeHS. If your project does not fit neatly into one of these questions, tell us what you need.
Last updated: 25 September 2026
What does BytecodeHS do?
BytecodeHS has two practices: Development and Security. We build custom web and mobile applications and APIs. We also take on authorized Linux and Android security testing and connected-device vulnerability research.
What kind of software can you build?
We build software around a specific business need, from web and mobile applications to APIs and integrations. You can come to us with an early idea or an existing specification. We will discuss the problem, what already exists, and the result you need before proposing a scope.
Can you work with an existing system?
Possibly. Send a short description of the system and the change you need. We will review the technical fit and the access required before committing to the work.
What security work can you take on?
We take on authorized penetration testing of Linux and Android systems and vulnerability research on connected devices. Before testing, we agree on the systems in scope, who can authorize the work, the testing boundaries, and how findings will be reported.
How does a project start?
Send us a short outline through the contact form or by email. We will discuss your goals, constraints, and any existing system. If the project is a fit, we will prepare a written proposal; work starts once the scope and agreement are in place.
How are price and timeline decided?
They depend on the work. After we understand the scope, we can propose deliverables, a schedule, and a price or pricing structure. The signed agreement records what is included and how changes will be handled.
Will you keep our project confidential?
We do not publish a client's name, project details, or security findings without the relevant permission. Some of our security work is described publicly only in anonymous terms. If you need an NDA, tell us before sharing confidential material so we can agree on the terms first.
How should we send sensitive information?
Start with a high-level note to security@bytecodehs.net. Do not put credentials, unpublished vulnerability details, or other secrets in the public contact form. We can agree on a secure way to exchange technical material before you send it.
Which address should we use?
For software projects and general enquiries, write to sales@bytecodehs.net. For security testing or vulnerability research, write to security@bytecodehs.net. You can also use the contact form on the main site for an initial enquiry.