About us
We're an Italian software house founded by people who have always built software: over twelve years working side by side, from large corporates to startups.
In over twelve years together we've worked across every kind of setting: consulting engagements and our own products, dozens upon dozens of different cases, each with its own constraints, deadlines and lessons.
We assemble the team around the project, drawing on our network of senior developers: the work decides the size, not an org chart. Whatever its composition, technical responsibility stays with CODEPRESS.
We work fully remotely, with clients in Italy and abroad. We believe in transparency: a written scope, clear timelines and costs, direct communication, code we stand behind over time.
What else we do
The packages cover what can be bought with a closed scope. The company also works in other areas, which we run for the clients we already serve:
- IT consulting: needs analysis, architecture, digital transformation
- Technical training for teams, entirely remote
- Hosting, cloud and infrastructure management
- Migration of data, applications and authentication systems
- Digital commerce: licences, subscriptions, hardware and services
- Digital content and marketing, classic SEO and SEO for AI engines
- Research and development on artificial intelligence, automation and emerging technologies
From idea to production
We cover the entire software lifecycle, with the same care at every stage:
- Requirements gathering
We listen and turn real needs into clear, measurable goals.
- Analysis & design
We design solid architectures, built to last and to evolve.
- Implementation
We write clean, maintainable code with frequent releases.
- Advanced testing
We test thoroughly, so software reaches production reliably.
- Delivery
We ship to production and support the software over time.
Frequently asked questions
How does a project with you start?
With a 20-minute technical call, no strings attached: we work out the problem you're facing and tell you straight away which of the seven packages covers it, or whether it needs clarifying first. If the package fits, you receive a written proposal with the scope defined, the price and the delivery date, ready to sign.
Are the published prices final?
For audits and the PoC, yes: the scope is fixed and so is the price, agreed before the work starts. For refactoring, feature development and AI work we publish the starting threshold instead, because the final cost depends on how wide a scope we agree on together.
Do you work remotely?
Yes, we work entirely remotely and don't offer an on-site option: we don't travel to a client's office, and we don't ask anyone to work from ours. We collaborate with companies in Italy and abroad, with no office or geographic constraints. The registered office listed in the site footer is a company-registry fact, not a place where any work actually happens.
Do you offer support after the release?
Yes. Every package can include maintenance, monitoring and evolution of the software after delivery: we don't disappear on release day. Software needs managing over time because the data, the traffic and the dependencies around it keep changing, not writing once and leaving it to run on its own. We talk about it at the end of each engagement, based on what's actually needed.
Do you also work on existing systems?
Yes. Most of our work starts from software that already exists, not from a blank page: we read it with an audit, secure it, evolve it with new features, or put it right with a targeted refactor, without unnecessary rewrites. The code you already have in production stays the starting point, not an obstacle to throw away and rebuild from zero.
What kind of contract do you work under?
Every package starts from a scope written down before we sign: what is in, what is out, what we deliver and by when. Price and date are agreed upfront, inside that scope, and don't change once work has started. If something outside the scope shows up while we work, we flag it when it happens, with a separate estimate: it never lands as a surprise line at delivery. That holds on every package, not just some.
Who owns the code you write?
Yours, whenever a package produces code: we don't retain rights over what we write, and being able to use it later never depends on keeping a contract with us running. Depending on the package, the code either lands straight in your own repository as we go, or we hand over the source at delivery: nothing we write stays accessible only by going through us. What stays ours is the technical responsibility for that code, not a claim over it.
Who actually works on the project?
Not two fixed developers who work every project: we assemble the team around the project, drawing on our network of senior developers, and the work decides the size, not an org chart set in advance. Whatever composition we choose, technical responsibility for that code stays with CODEPRESS, not with whoever happened to write it that day: that responsibility is what you're buying alongside the package, not a specific name pencilled into a calendar.