AI & agents
New ways to work with intelligence
Explore agent frameworks, tool use, model interfaces and practical applications.
WASAME · The independent maker marketplace
Find the people behind
useful technology.
WASAME brings builders, capabilities, products, experiments and industry needs together. Explore what people make, how it works, the evidence behind it and where it can be used.
Explore what’s new ↗Bring your work to WASAME250Builder discovery candidates, not public profiles
18Industry landscapes
50Proposed Garage experiments
Explore WASAME
Find your way in
Start with a product, a capability, a problem or the people building something new.
Discover / Rising
Signals worth paying attention to.
Emerging tools, fast-moving categories and new capabilities gaining visibility. This is a discovery lens, not a ranking or endorsement.
Rising areas
Explore categories with active external discovery ecosystems.
Discover / New
Fresh thinking.
New things to explore.
Browse newly proposed concepts from the Garage and find the external catalogues where new makers and products are appearing.
Explore Garage concepts ↗Recently recovered concepts
These are proposals from source material, not products claimed to be built or launched.
Discover / Breakthroughs
Ideas that change what’s possible.
A place to surface meaningful advances in tools, research and applied technology. Listings will be evidence-led, with source and maturity made clear.
Edge & devices
Intelligence beyond the browser
Connected devices, embedded systems and ambient interfaces.
Research
Evidence into application
Research tools and methods that help ideas become useful capabilities.
Discover / Requests
What needs to be solved?
Real problems create the best starting points. This space is for buyer needs, industry challenges, build requests and open calls. No invented demand or customer briefs.
Bring a problem to the community
Tell us what is not working, what capability is missing or what you need built. Request intake is being connected to the shared WASAME / ZKUH process.
Describe a request ↗
Discover / Opportunities
Where capability meets opportunity.
Find pathways to collaborate, test, distribute, fund and apply useful work. Opportunities will be distinguished from verified offers, active calls and speculative leads.
01 / BUILD
People who turn ideas into things.
Discover independent developers, designers, studios, maintainers and specialist teams across software, hardware and emerging technology.
Builder communities
Discovery categories from the sourced candidate register. Individual profiles remain unpublished until identity, attribution and permission are confirmed.
01 / Systems
MCP & integrations
People creating interfaces, connectors and interoperable services.
02 / Intelligence
AI agents & frameworks
Agent builders, orchestration specialists and applied AI teams.
03 / Experience
Extensions & applications
Browser tools, scripts, web products, mobile apps and workflows.
250 discovery candidates recovered
Private working register only. Unclaimed and unverified. No personal profiles, private outreach details or implied consent are published here.
Builder Passports
Illustrative demo profiles showing how a maker connects to capabilities, products, experiments, evidence, collaborations and industries. These are not verified identities or public listings.
02 / THINK
Research, test and question assumptions.
Explore experiments, research tools and ideas that need evidence. The Garage is a working collection of proposed concepts, not a catalogue of finished products.
Garage experiments
Search the 50 recovered concepts by name, problem or experiment type.
03 / RUN
Tools and products made to be used.
Find software, utilities, extensions, devices and services. Product discovery should show what a thing does, who made it, its maturity and how to try it.
Product landscapes
Explore the product categories represented in current discovery sources.
Digital products
Apps & platforms
Web, mobile, desktop and SaaS products.
Browser ecosystem
Extensions & utilities
Small tools that improve a workflow or unlock a capability.
Connected systems
Edge & connected devices
Hardware, embedded systems and ambient computing.
Garage concepts are not yet products
The 50 proposed experiments are shown separately from verified products. No build, customer validation or commercial availability is implied.
Browse Garage ↗Products with their makers attached
Each listing connects the product to its builder, capability, evidence, dependencies and industry context.
04 / TRUST
Trust is built on evidence and permission.
Before anything is listed or distributed, establish who created it, what rights apply, what it does and whether it is safe to share.
Provenance
Identity & attribution
Know who is submitting, who contributed and where the work came from.
Assessment
Security & quality
Assess submitted artefacts before distribution or use.
Rights
Consent & commercial terms
Record permissions, licensing and agreed participation before publishing.
ZKUH qualification pathway
Designed intake and evidence boundary. The live site is not yet connected to automated ZKUH receipts, security scanning or rights approvals. Listings and checkout remain disabled until those controls operate.
05 / ACT
Move from discovery to doing.
Turn a problem into a request, connect with a builder, or bring a product forward for qualification and distribution.
Start a conversation ↗
Request
Describe a need
Explain the problem, constraints and outcome you need.
Connect
Find capability
Bring the right people and organisations into the conversation.
Distribute
Prepare to publish
Qualify products and establish rights before they reach buyers.
06 / KNOW · INDUSTRIES
Understand the world you are building for.
Explore industry landscapes, sector organisations and the environments where new products and capabilities can make a difference.
Industry landscapes
18 starting sectors and 54 organisation prospects recovered from the WASAME industry research. Prospects are not partners or endorsements.
Industry profile · Trades
Illustrative sector structure showing how demand, capabilities, builders and research connect. Demo data, not confirmed customer requirements.
Problems
Manual document handling · Fragmented tools across teams · Slow adoption of proven capabilities
Requests
Summarise trades paperwork · Mobile-first field capture
Capabilities
Tender Signal Extractor · Demo relationship only
Products
No packaged products yet in this illustrative sector profile.
Builders
Sana Reyes @sana.tender · Demo passport, not a verified public profile
Research
Open papers relevant to this sector · To be curated
Opportunities
Package existing capabilities into a sector product · Pilot with a founding customer
07 / IDENTIFY
Find the people and organisations behind it.
Builder discovery starts with public work and clear attribution. Public profiles only appear when the person or organisation has been verified and has agreed to publication.
Makers
Independent builders
Individual makers, developers, designers and maintainers.
Teams
Studios & organisations
Product companies, specialist teams and research groups.
Communities
Networks & communities
Groups that help makers share knowledge and find opportunities.
250 private discovery candidates
These records are not public Builder Passports. The public directory will grow through verified identity, attribution and explicit publication permission.
08 / REACH
Take good work further.
Connect with communities, channels and distribution partners. Build reach through relevant relationships, not indiscriminate promotion.
Communities
Meet relevant networks
Industry groups, maker communities and professional associations.
Channels
Find distribution
Platforms and channels that help useful products reach their audience.
Partners
Build partnerships
Technology, delivery and ecosystem relationships with clear terms.
09 / EDGE
Find the next useful capability.
Explore external catalogues, open ecosystems and specialist tools. These sources help discovery; they are not WASAME listings or endorsements.
External discovery directories
Open a source to explore its catalogue. Provider-reported counts are not WASAME inventory.
Connect with WASAME
Have a question, idea or introduction?
Tell us what you are looking for, what you have built or who should be part of the conversation.
Ask WASAME
Shared intake and CRM integration are being connected. The public submission form will be enabled when it can issue a durable receipt and route the request to an accountable owner.
Sell on WASAME
Your work deserves the right audience.
Bring a product, tool or service forward for assessment and distribution. We establish identity, provenance, security and rights before public listing.
Seller onboarding
Seller intake is designed around ZKUH receipts, security assessment, ownership and rights checks. Public listing, checkout and payouts remain disabled until those controls and commercial agreements are operational.
The WASAME journey
From discovery to trusted distribution.
WASAME brings useful products and their creators into a managed path: identify, submit, assess, establish rights, publish, sell and reward the people behind the work.
One process. Clear gates.
Each stage has its own owner, decision and evidence. Passing one stage does not silently approve the next.
01 · Discover
Find the work and its makers
Discover software, apps, scripts, agents, MCP services, extensions and other useful products. Identify the actual owner, maintainer and contributors.
02 · Submit
Bring it to Zkuh
The owner or authorised representative provides the package, source, documentation, permissions and relevant context. A receipt records what was received.
03 · Assess
Test and qualify
Zkuh inspects the submission, records the scope and runs applicable checks. Findings, exceptions and retest outcomes are retained as evidence.
04 · Establish rights
Agree what WASAME may do
Ownership, authority, licence scope, distribution, support, updates and commercialisation rights are documented separately from technical test results.
05 · Accept & reward
Record the owner arrangement
Where accepted into the programme, the originator reward and any ongoing participation are recorded against the specific product and signed terms.
06 · Publish & distribute
Make it available
WASAME prepares the listing, pricing, documentation, buyer terms, delivery path and support information. Publication follows the required approvals.
07 · Buy & use
Clear buyer checkout
Buyers see the seller/contracting party, price, currency, licence, renewals, delivery and refund terms before committing.
08 · Account & distribute rewards
Keep a traceable record
Sales, fees, refunds, settlement, owner rewards and any ongoing group participation are reconciled with receipts and the applicable agreement.
What this is not
A Zkuh submission receipt is not a test pass. A test pass is not a licence. A licence is not a listing approval. A listing is not a sale. A payment instruction is not a settled payment.
ZKUH · Zero-Knowledge Utility Hub
Test what is submitted.
Prove what was checked.
Zkuh is WASAME's separate intake, validation and assurance programme. It helps identify the product, inspect it, test it and produce evidence-backed findings before commercial consideration.
The Zkuh assessment pathway
Checks are scoped to the product, source, permissions and available test environment. No blanket guarantee of safety is implied.
Intake
Identify & preserve
Record the submitter, actual owner, source location, version, package digest, licence claims, dependencies and submitted artefacts.
Static review
Inspect the package
Review code, dependencies, build configuration, permissions, data access, network behaviour and suspicious or potentially harmful functionality.
Controlled testing
Exercise behaviour
Where technically supported, run controlled tests for bugs, vulnerabilities, unexpected behaviour, policy concerns and potentially unlawful use.
Human review
Assess findings
Classify risks, evidence, exceptions, unresolved issues and remediation. Escalate matters that need specialist or legal judgement.
Disposition
Pass, conditional, fail or quarantine
Issue an assessment outcome for the tested version and stated scope. Support correction, retest, appeal and revocation.
Assistant
Zkuh guides the submitter
Explain required inputs, help complete the submission, identify missing evidence, translate findings into plain language and guide remediation. It does not approve its own work.
Separate rights gate
After technical assessment, WASAME separately verifies the relevant owner, authority to submit, intellectual property position and permission to use, distribute or commercialise the product. The owner retains rights except to the extent expressly granted in the signed agreement.
What a Zkuh receipt contains
Submission identity, version and digest; scope; test methods and tool versions; findings; evidence references; exceptions; assessor and approval; disposition; expiry or revalidation triggers; and a verifiable receipt identifier.
For builders, owners and contributors
Your work has value.
Rewards need to be clear.
WASAME's programme recognises the people who originate useful products and the groups who help them grow. The arrangement is recorded product by product.
Two distinct reward stages
These are separate from ownership of the underlying intellectual property.
At acceptance
Originator reward
When a product is accepted into the WASAME programme, the originating owner may receive the agreed initial reward. The amount, timing, conditions, currency and tax treatment are set out in the product-specific agreement before acceptance.
As it grows
Ongoing participation
Where agreed, subsequent owners, groups or contributors may participate in future value generated by the product. Beneficiaries, attribution, calculation, duration and adjustment rules must be documented, not assumed.
What a builder can expect to see
Before signing
Product identity and version · owner and rights position · initial reward · any ongoing participation · what WASAME may do · support and update responsibilities · term, withdrawal and termination.
For every transaction
Gross amount and currency · taxes · discounts · payment fees · refunds and chargebacks · amount eligible for distribution · reward calculation · beneficiary allocation · settlement state.
For every payout
Payee identity and payment details held securely by the payment provider · amount · currency · deductions · payout reference · status · date · receipt and reconciliation.
No hidden commission promise
WASAME will show the actual product-specific reward and commercial terms before the owner agrees. No percentage, minimum payout, recurring entitlement or group allocation is implied by this explanatory page. The historic reward schedule and group participation rules are being reconciled into the controlled agreement register.
How the money moves
Buyer payment → payment provider confirmation → order and receipt record → applicable costs, taxes, refunds and fees reconciled → agreed owner and beneficiary allocation → payout instruction → settlement confirmation → payout receipt.
Buyer experience
Know what you're buying.
Before you pay.
Every purchase should make the product, contracting party, price, currency, licence, delivery, support and refund conditions clear before payment.
Checkout sequence
A buyer should be able to review the complete commitment before a payment is initiated.
01
Product & version
Confirm the exact product, edition, version, compatibility and what is included.
02
Price & billing
Show total price, currency, GST or other applicable taxes, recurring charges and renewal date where relevant.
03
Licence & terms
Present the applicable product licence, buyer terms, support, use restrictions and refund policy.
04
Review & confirm
Capture affirmative acceptance of the applicable versioned terms and a clear final order summary.
05
Payment & receipt
Use the payment provider for secure payment details. Record authorisation, settlement, failure or refund separately.
06
Delivery & support
Provide the promised download, access or service, a purchase receipt, support route and order history.
Checkout is not yet accepting payments
The public product catalogue is in place, but payment processing, order ledger, tax invoicing, refunds and seller/owner settlement are not yet connected end to end. No purchase button should imply that money can currently be taken.
WASAME · Legal & governance
Clear rights.
Clear responsibilities.
The Legal Centre brings marketplace rules, creator arrangements, buyer protections, privacy and product-specific licences into one controlled document register.
Document status
The documents below are the required controlled set. Existing source material is being reconciled into them. They are not represented as final, legally approved or currently accepted terms until the relevant version, contracting entity, approval and effective date are published.
Marketplace and participation
Rules for using WASAME and participating in its product and builder programme.
Draft register
Marketplace Terms of Service
Access, accounts, acceptable use, marketplace role, listings, availability, service changes, liability, complaints, suspension and termination.
Product-specific agreement
Owner Submission & Commercialisation Agreement
Authority, provenance, retained ownership, rights granted to WASAME, permitted use, distribution, sale, support, updates, warranties, reward and termination.
Controlled schedule
Originator Reward & Participation Schedule
Initial acceptance reward, ongoing participation, beneficiary groups, attribution, calculation basis, adjustments, reporting and settlement.
Buyer terms
Buyer Terms & Product Licence
Contracting party, product scope, permitted use, subscriptions, renewal, delivery, support, cancellation, refunds and consumer rights.
Privacy
Privacy Policy & Data Notice
Information collected, purposes, sources, disclosures, processors, overseas handling, access, correction, retention, deletion and contact route.
Trust
Acceptable Use, Security & IP Policy
Prohibited activity, security findings, vulnerability reporting, infringement notices, takedowns, appeals, revocation and incident handling.
Payments
Payments, Refunds & Payout Policy
Payment processing, taxes, fees, refunds, chargebacks, reward calculation, payout timing, failed payouts and reconciliation.
Participation
Membership & Contributor Terms
Membership status and benefits, contribution recognition, permissions, communications, voluntary participation and withdrawal.
Existing corporate policies
Tech 4 Humanity publishes corporate website Terms of Service and a Privacy Policy. Those documents relate to the corporate website and its published services; they are not a substitute for the WASAME product, owner, buyer, distribution or payment agreements.
Tech 4 Humanity Terms of Service ↗ · Tech 4 Humanity Privacy Policy ↗
Document control required before publication
Each document must carry the legal entity, owner, version, approval status, effective date, covered participant types, acceptance event, change history and linked workflow. Material changes require renewed acceptance where appropriate.
Legal approval gate
Before live sales or binding acceptance, the contracting legal entity, jurisdiction, seller/distributor role, tax treatment, product rights, reward rules and consumer obligations must be verified and reviewed by an appropriately qualified lawyer. This page is an index, not a substitute for the agreements.
Contact & corporate information
Talk to WASAME.
For product submissions, builder participation, partnerships, buyer support, rights enquiries or media and corporate matters.
Corporate context
Tech 4 Humanity
WASAME is part of the Tech 4 Humanity product portfolio. Corporate background and organisation information are available through the official Tech 4 Humanity website.
General enquiries
Contact the team
Published corporate contact: Level 6, 25 King St, Bowen Hills, Brisbane, QLD 4006. See the corporate privacy page for the published address record.
Product and builder support
Submissions & support
Product submissions will enter through Zkuh. Product owners can request an assessment, provide evidence, respond to findings and review the outcome before any commercial agreement is proposed.
Corporate identity disclosure
The published corporate contact is troy@tech4humanity.com.au. The published corporate privacy page lists Level 6, 25 King St, Bowen Hills, Brisbane, QLD 4006. The exact contracting legal entity and ABN/ACN for WASAME transactions still need to be confirmed against the approved corporate record before checkout or agreements go live.
W · WEB
Web tools built for real work.
Independent web products, hosted tools, SaaS utilities and practical interfaces. See the builder, capability, evidence and route to use.
Web capabilities & products
Demo catalogue records. Builder attribution and evidence are illustrative until independently verified.
A · APPS
Applications with a job to do.
Focused applications, business tools and cross-platform products, with the people and proof behind them.
Apps & application capabilities
Demo catalogue records, not live commercial offers.
S · SCRIPTS
Small tools. Useful leverage.
Scripts, automations, command-line utilities and repeatable workflows that remove friction from specific tasks.
Scripts & automations
See what each tool does, what it needs and who is developing it.
A · AGENTS
Agents that do more than chat.
Task-specific agents, agent workflows and runtime capabilities. Understand inputs, outputs, dependencies, permissions and evidence.
Agent capabilities
Demo records distinguish prototype claims from verified operation.
M · MCP
Connect tools, systems and context.
MCP servers, clients and integrations with visible tool surfaces, permissions, dependencies and trust evidence.
MCP capabilities & integrations
Discovery does not imply security review, maintenance or endorsement.
E · EXTENSIONS
Useful capability, where you work.
Browser extensions, sidecars and ambient utilities that bring focused functions into the user's existing environment.
Extensions & sidecars
Show the maker, permissions, supported channels and tested status.
WASAME browser companion
The first click should explain the value, not leave someone guessing what the extension does.
First click · Welcome
Your browser is where the work happens.
The popup introduces WASAME as a companion beside the browser. It explains capture, contextual assistance and access to the wider tool workspace, with an explicit action to open the side panel.
First-use explanation can be dismissed and remembered. It remains available through the extension menu.
Everyday use
Capture, understand, connect
Open the side panel to access Browser, Search, Media, Zkuh and Tools. The popup displays the active page title and site for context. Page content is not sent until the user chooses an action.
Trust boundary
Visible and permission-led
The extension must make clear what context it can see, what is sent, which service receives it and whether the action is local, queued or acknowledged. No silent collection or assumed consent.
Extension release status
The onboarding popup and side-panel entry are being built in the local extension source. A successful package build, browser installation, toolbar-click test and verified backend action are required before the extension can be described as released or operational.