zasky
DEEN

The Austrian and European software marketplace.

Publish your project. Vet the providers. Receive everything, documented.

Zasky is being built as a marketplace for companies that need software and do not have an IT department of their own. This page exists to find the first clients and providers before launch.

Get project updates

Three problems, stated plainly.

Written from the desk of a managing director without an IT department.

I do not know what to specify.

A requirement written in prose is not a specification. Without one, offers cannot be compared and the scope stays open until the final invoice arrives.

I do not know who to trust.

Every provider states the same qualifications. None of it is checked by anyone, and a reference given over the telephone is not evidence.

I do not know what I will actually receive at the end.

Source code, access credentials, licences, documentation. Which of these change hands is usually settled after the work is finished, if at all.

AI has lowered the barrier to building software. It has raised the barrier to commissioning the right software and receiving it properly at the end. Zasky is built for that second barrier.

How it works.

Four steps, from the first line of the brief to the signed handover.

  1. 01

    Define requirements

    You describe the result you need and the conditions a provider must meet. Zasky turns that into a structured tender.

  2. 02

    Receive bids from vetted providers

    Only providers who meet your conditions may submit. Every bid carries the badges and the status of its provider.

  3. 03

    Select a provider

    You compare bids against the same specification. Scope, price, deadlines and the handover are agreed in writing before work starts.

  4. 04

    Documented handover

    Source code, access, licences and documentation are recorded in a protocol and signed by both parties.

Who is allowed to bid.

You set the conditions a contractor must meet before a single bid arrives. Company size, place of business, verified references, licences on file, sector experience, maintenance capacity.

The same mechanism carries a small assignment for a sole trader and a large tender that only a certified organisation may answer. The requirements are yours to set, and you can see exactly whom they rule out.

Requirement filterExample
Requirements a provider must meet

6 of 8 providers meet your requirements.

  • Provider AEstablishedReferencesLicencesEU
  • Provider BVerifiedReferencesLicences
  • Provider CEstablishedLicencesIdentity
  • Provider DVerifiedReferences
  • Provider ERegisteredEU
  • Provider FEstablishedReferencesSign-off
  • Provider GVerifiedIdentityEU
  • Provider HRegisteredLicences

Trust: badges and status.

Two separate things. Badges record what Zasky has checked. Status records what a provider has completed.

Badges

A badge is issued once the evidence behind it has been examined. It is not entered by the provider.

  • References verified

    At least three completed projects, each confirmed in writing by the client who commissioned it.

  • Licences on file

    Trade licence and, where the work requires one, the professional qualification held on record.

  • EU place of business

    Registered office and tax registration inside the European Union, checked against the company register.

  • Identity confirmed

    Authorised signatory checked against an identity document and against the register entry.

  • Sign-off record documented

    At least one project closed on Zasky with a complete handover protocol signed by both parties.

Planned verification process

Status

Status grows with completed projects and client count. It does not replace your judgement; it makes experience visible. A provider with two finished projects is not excluded, and is simply recognisable as what it is.

  • Registered

    Account created, company data entered.

    May bid on projects that carry no conditions.

  • Verified

    Identity, licences and place of business checked against documents.

    Passes requirement filters that ask for verified providers.

  • Established

    Five projects closed on Zasky with a signed handover protocol.

    Project count and client count are shown on the profile.

  • Reference partner Planned

    Twenty closed projects and a verified reference from the same sector.

    Eligible for large tenders and framework agreements.

The handover.

Projects rarely fail while the work is being done. They fail at the end, when nobody wrote down what changes hands.

The repository stays with the agency. Two domains sit in a private account. A licence was bought in somebody’s name and nobody knows whose. The handover is the moment of risk, and it is usually the only part of the project that was never specified.

On Zasky it is a fixed step with a fixed form. The project is not closed until every row is confirmed by both sides.

Handover protocolProject 2026-0148
Source code
Repository, full history
Access
Servers, domains, services, accounts
Licences
Including transfer of usage rights
Documentation
Operations, architecture, dependencies
Sign-off record
Signed by both parties
Handed over on

Example, planned form

The network.

Zasky connects providers with each other, so that joint bids and subcontracting are part of the model rather than an exception.

On the other side it opens the industry to companies in manufacturing, retail, healthcare, the trades and logistics, which usually have no route into it at all.

Austrian, therefore European.

Contracts concluded through Zasky are governed by law that applies where you do business, and a dispute is heard by a court you can reach. Platforms registered outside Europe operate under different law and a different data regime. That is a factual difference, and it is worth knowing before a contract is signed.

Place of business
Austria, European Union
Governing law
Austrian contract law, EU consumer law
Data protection
DSGVO/GDPR, servers located in the EU
Billing
Euro, Austrian invoicing rules, VAT ID checked

What each side receives

For clients

Requirements before bids
You decide who may bid, before the first offer arrives.
Comparable offers
Every bid answers the same specification, so price means the same thing across all of them.
Checked providers
Identity, licences and place of business are verified by Zasky, not stated by the provider.
A documented ending
Source code, access and licences change hands on the record, in one protocol.

For providers

Fewer unsuitable enquiries
Requirement filters remove the projects you could not take on anyway.
Evidence instead of claims
Badges and status are issued on checked evidence and cannot be self-declared.
Work with other providers
Joint bids and subcontracting are supported, so a small team can answer a large tender.
A clear closing
The handover protocol records what was delivered and when, which ends the argument about scope.

Where the project stands.

  • Concept and legal frameworkQ1 2026Complete

    Business model, terms of use and the contract structure between client, provider and platform are drafted.

  • Platform corefrom Q2 2026Under way

    Tenders, requirement filters, bids and the handover protocol are being implemented.

  • Verification and badgesQ2 2027Planned

    The checking procedure behind each badge is being written, together with the evidence it requires.

  • Closed betaQ3 2027Planned

    A limited number of clients and providers run real projects end to end.

Anyone on the update list is informed at every step and can help shape the beta.

Questions.

When does Zasky launch?

The closed beta is planned for the third quarter of 2027. A public launch date is not fixed, because it depends on the verification procedure being finished and reviewed. As soon as a date is set, everyone on the update list receives it.

What does it cost to use?

Publishing a project is planned to be free for clients. Providers pay a fee on concluded projects. The rate is not decided yet. It will be published in full before the beta opens, not afterwards.

Who owns the source code at the end?

The client, unless the contract states otherwise. Transfer of usage rights is a separate row in the handover protocol and has to be confirmed by both parties. Third-party licences are listed individually with the conditions attached to them.

How are providers vetted?

Identity, company register entry, trade licence and place of business are checked against documents. References are confirmed with the client who gave them, in writing. The full procedure is still being written and will be published before the beta.

What happens in a dispute, or if a provider drops out?

The rules are being drafted with legal counsel. Planned: payment released against milestones, an escalation step inside Zasky before any court, and a documented state of the work at every milestone so that a second provider can continue. None of this is settled yet, and it will not be presented as settled until it is.

I have no IT department. Can I still publish a project?

Yes. That is the case Zasky is built for. The requirement form asks about the business problem, the budget and the deadline, not about frameworks or architecture. Providers translate that into a technical proposal, and the proposals stay comparable because they answer the same form.