Squeezer

Squeezer is a platform that helps software developers build apps easily without tackling the entire blockchain infrastructure.

About Squeezer

Squeezer aims to integrate microservice architecture and blockchain functionality, so as to enable developers to easily connect to “any blockchain (such as BTC, ETH, or LTC)” and conduct blockchain transactions without having to deal with blockchain development. The organization plans to develop connectors capable of triggering blockchain events, and a platform that will “compile and deploy apps in multiple stages directly from GitHub or other code repositories.” SQZR tokens will be used to access and deploy applications on the Squeezer platform.

Token Sale Use of Blockchain

Product

1.8
Product
Readiness

Is the product ready for use? Is there a working prototype or MVP? How long until it is operational?

2.0
N/A
2 - Proof of concept or test platform.
Appeal

How appealing is the product? How good or necessary is it? Does it have a distinct edge?

2.0
N/A
2 - Meh, okay.
Target User Base

Is it mass market or niche?

2.0
N/A
2 - Small audience / niche market.
Competition

Are there many other similar solutions or is this one of just a few, or even one of a kind?

2.0
N/A
2 - Quite a few / somewhat better competitors.
Innovation

How innovative or inventive is the product, either conceptually or technologically?

1.0
N/A
1 - None or indeterminate.

Product

Squeezer is “powered by microservices platforms, such as AWS Lambda and Google Functions, which means that the auto-scalability feature is enabled by default”. However, it is noted towards the end of the document that “the Squeezer Framework does not have any legal or partner qualification with the specified cloud providers”. Squeezer’s target user base is fairly limited compared to other blockchain-related projects. The level of competition that Squeezer faces, as a service that aims to simplify application development with blockchain technology, is considerable. The Squeezer GitHub page is provided and contains high levels of content and activity. The repository for the minimum viable product is also included.

Product Whitepaper

Use of Blockchain

2.4
Use of Blockchain
Blockchain Development

Is blockchain technology essential? Does it make the solution significantly different and better?

2.0
N/A
2 - Some smart contract functionality.
Disruptive Blockchain Advantage

How disruptive is the introduction of blockchain technology into the product's market space?

3.0
N/A
3 - Potentially disruptive.
Need for a Custom Token (vs. BTC or ETH)

Is the token essential or could it be done just as well or better with fiat or Bitcoin?

1.0
N/A
1 - None really, just fundraising.
System Decentralization (besides token)

How decentralized is the system architecture other than the token (e.g., data collection, storage, access, and use, or decision making processes, etc.)?

4.0
N/A
4 - Mostly decentralized.
Contribution to Blockchain Ecosystem

How compelling is the solution's contribution to the evolution of blockchain infrastructure and economy?

2.0
N/A
2 - Meh, okay.

Use of Blockchain

SQZR is an ERC20 compliant token and is used to access and deploy applications using the Squeezer framework. Currently the Squeezer framework is operational for web projects, but the organization is working to develop connectors so that a microservice can trigger an action on the blockchain. As a result, there is no significant need to create a custom token other than to generate funds for the platform.

Use of Blockchain Roadmap

Whitepaper

2.6
Whitepaper
Comprehensiveness

Does it cover the full scope of the problem and solution?

2.0
N/A
2 - Insufficient coverage.
Readability

Is it easy enough to understand?

4.0
N/A
4 - Easy to read and understand.
Transparency

Does it candidly describe and disclose where the project now stands, how much exists and how much still needs to be done, etc.?

2.0
N/A
2 - Ambiguous non-disclosure.
Business Plan Presentation

Does it contain a viable, comprehensive business plan?

3.0
N/A
3 - More information required.
Technology Presentation

Does it present a well thought out technological architecture? Does it address implementational challenges?

2.0
N/A
2 - Missing critical information.

Whitepaper

The whitepaper is 32 pages in length. There is a lack of specific technical discussion provided in the document. The discussion regarding technical architecture is made on a layman basis. The business plan is presented with moderately low levels of detail. The market research is fairly brief. However, there is a table included that compares Squeezer with four competitors (Serverless, ClaudiaJS, Stdlib, and Apex). Overall, the whitepaper primarily discusses the features of the platform and the justification for the service, but lacks detail.

Whitepaper Compliance

Roadmap

3.0
Roadmap
Concreteness

Is there a concrete and practical development plan (vs. just a conceptual vision)?

3.0
N/A
3 - An overall plan, major milestones stated.
Feasibility

Is the development plan realistic? Is it based on reasonable goals and timelines?

4.0
N/A
4 - Realistic.
Vision

Is there a larger, long-term vision?

3.0
N/A
3 - A trend with potential.
Dependencies (services or capabilities)

How available, operational, or trusted are the other systems or capabilities on which the project relies?

2.0
N/A
2 - Not fully available or trustworthy.
Current Position

Where is the project now, relative to its vision and plans?

3.0
N/A
3 - Getting there.

Roadmap

The roadmap on the Squeezer website spans from February 2016 to April 2019. There are 8 milestones presented in total. Notable completed achievements include the development of the proof-of-concept and plugin integration. The blockchain cloud components and connectors are set to launch in February 2019. Subscription purchases and the ability to build blockchain-connected applications are set for April 2019.

Roadmap Company and Team

Compliance

2.8
Compliance
Token Utility (value through usage)

How much use is there for the token itself (regardless of its value as an investment vehicle)?

2.0
N/A
2 - Minimal or contrived.
Token as Security (tradable instrument)

How valuable is the token as an investment vehicle or financial instrument?

2.0
N/A
2 - Primarily, with few additional rights.
Token/Smart-Contract Readiness

Is the blockchain infrastructure of the project ready for use? Is there a working prototype or MVP? How long until it is operational?

2.0
N/A
2 - Proof of concept or test platform.
Attention to Compliance Issues

How much attention is given to compliance (via token and ecosystem design, token sale participation, etc.)? Is this issue addressed directly and coherently?

4.0
N/A
4 - Specific, detailed.
Legal Review/Risk Assessment

What kind of legal documentation (reviews or agreements) and risk assessment are provided?

4.0
N/A
4 - Professional.

Compliance

There are approximately 3 pages towards the end of the document discussing legal considerations. There is also a separate 15-page document that outlines the terms of use for the platform and token sale, which is fairly comprehensive and professionally written. It is stated that “the Squeezer Framework does not have any legal or partner qualification with the specified cloud providers”. It is stated that SQZR should not be considered security tokens. KYC will be used for the token sale.

Compliance Token Sale

Company and Team

3.0
Company and Team
Company Stage and Foundation

Is the company already established? Has it raised funds before? Is it mature?

3.0
N/A
3 - Company structure in place.
Background of Lead Team Members

Do we know who they are? Do they have LinkedIn profiles? Do they have solid, relevant backgrounds?

3.0
N/A
3 - Minimally sufficient.
Team Assembly and Commitment

Is a solid, fully committed core team in place? Do they have online (e.g. LinkedIn) profiles showing sufficient relevant experience? Is their participation transparent?

3.0
N/A
3 - Mostly assembled and committed.
Team Skill Set Relevance

Does the amount of talent and skill in each area seem to fit the project requirements?

3.0
N/A
3 - Correlated to project requirements.
Team Skill Set Balance

Is the team well-rounded (biz/tech/blockchain)? Is there sufficient talent and skill in all areas of required development?

3.0
N/A
3 - Somewhat uncertain, probably okay.

Company and Team

The core team of 7 individuals is listed on the Squeezer website, along with their profile pictures, job titles, and links to LinkedIn profiles. The skill set of the core team is comprised mainly of a background in business development. There are two individuals with a technical background, one of which is the CEO, who has prior blockchain experience as a consultant. The team is not fully developed as there are plans to hire additional developers to build the blockchain cloud connectors in July 2018.

Company and Team Product

Token Sale

2.8
Token Sale
Raise Amount Max

Is there a clear cap? Is the maximum raise amount modestly sufficient (as opposed to either greedy or insufficient)?

2.0
N/A
2 - Somewhat greedy or unrelated to plans.
Raise Amount Min

Is the minimum raise reasonable considering the development plan? Are there raise-amount dependent milestones?

2.0
N/A
2 - Only loosely related to plans.
Fund Allocation

Is fund distribution and allocation reasonable and justified?

3.0
N/A
3 - Rough estimates, but sensible.
Token Allocation

Is the ratio of tokens sold to those kept reasonable? Does it prevent the company from having too much control?

3.0
N/A
3 - Sufficient company/community interest balance.
Media Presence and Following

Is the sale being talked about in Reddit, Bitcointalk, Social Media, Medium, etc.? Is information available and accessible? Is there interest?

4.0
N/A
4 - Solid exposure and interest, good impression.

Token Sale

The total number of SQZR tokens is 385 million (40% is for sale, 34% is for the organization, 20% is for the team, 5% is for advisors, and 1% is for the bounty program). Vesting periods are not clearly outlined. The allocation of funds is briefly described (45% is for technical development, 30% is for non-technical staff, 10% is for marketing expenses, 8% is for infrastructure expenses, and 7% is for operating expenses). The soft cap is 7.7 million SQZR and the hard cap is 154 million SQZR, where 1 SQZR = $0.20 USD.

Product

Squeezer is “powered by microservices platforms, such as AWS Lambda and Google Functions, which means that the auto-scalability feature is enabled by default”. However, it is noted towards the end of the document that “the Squeezer Framework does not have any legal or partner qualification with the specified cloud providers”. Squeezer’s target user base is fairly limited compared to other blockchain-related projects. The level of competition that Squeezer faces, as a service that aims to simplify application development with blockchain technology, is considerable. The Squeezer GitHub page is provided and contains high levels of content and activity. The repository for the minimum viable product is also included.

Category Breakdown
Readiness

Is the product ready for use? Is there a working prototype or MVP? How long until it is operational?

2.0
N/A
2 - Proof of concept or test platform.
Appeal

How appealing is the product? How good or necessary is it? Does it have a distinct edge?

2.0
N/A
2 - Meh, okay.
Target User Base

Is it mass market or niche?

2.0
N/A
2 - Small audience / niche market.
Competition

Are there many other similar solutions or is this one of just a few, or even one of a kind?

2.0
N/A
2 - Quite a few / somewhat better competitors.
Innovation

How innovative or inventive is the product, either conceptually or technologically?

1.0
N/A
1 - None or indeterminate.
Product Score:
1.8

Use of Blockchain

SQZR is an ERC20 compliant token and is used to access and deploy applications using the Squeezer framework. Currently the Squeezer framework is operational for web projects, but the organization is working to develop connectors so that a microservice can trigger an action on the blockchain. As a result, there is no significant need to create a custom token other than to generate funds for the platform.

Category Breakdown
Blockchain Development

Is blockchain technology essential? Does it make the solution significantly different and better?

2.0
N/A
2 - Some smart contract functionality.
Disruptive Blockchain Advantage

How disruptive is the introduction of blockchain technology into the product's market space?

3.0
N/A
3 - Potentially disruptive.
Need for a Custom Token (vs. BTC or ETH)

Is the token essential or could it be done just as well or better with fiat or Bitcoin?

1.0
N/A
1 - None really, just fundraising.
System Decentralization (besides token)

How decentralized is the system architecture other than the token (e.g., data collection, storage, access, and use, or decision making processes, etc.)?

4.0
N/A
4 - Mostly decentralized.
Contribution to Blockchain Ecosystem

How compelling is the solution's contribution to the evolution of blockchain infrastructure and economy?

2.0
N/A
2 - Meh, okay.
Use of Blockchain Score:
2.4

Whitepaper

The whitepaper is 32 pages in length. There is a lack of specific technical discussion provided in the document. The discussion regarding technical architecture is made on a layman basis. The business plan is presented with moderately low levels of detail. The market research is fairly brief. However, there is a table included that compares Squeezer with four competitors (Serverless, ClaudiaJS, Stdlib, and Apex). Overall, the whitepaper primarily discusses the features of the platform and the justification for the service, but lacks detail.

Category Breakdown
Comprehensiveness

Does it cover the full scope of the problem and solution?

2.0
N/A
2 - Insufficient coverage.
Readability

Is it easy enough to understand?

4.0
N/A
4 - Easy to read and understand.
Transparency

Does it candidly describe and disclose where the project now stands, how much exists and how much still needs to be done, etc.?

2.0
N/A
2 - Ambiguous non-disclosure.
Business Plan Presentation

Does it contain a viable, comprehensive business plan?

3.0
N/A
3 - More information required.
Technology Presentation

Does it present a well thought out technological architecture? Does it address implementational challenges?

2.0
N/A
2 - Missing critical information.
Whitepaper Score:
2.6

Roadmap

The roadmap on the Squeezer website spans from February 2016 to April 2019. There are 8 milestones presented in total. Notable completed achievements include the development of the proof-of-concept and plugin integration. The blockchain cloud components and connectors are set to launch in February 2019. Subscription purchases and the ability to build blockchain-connected applications are set for April 2019.

Category Breakdown
Concreteness

Is there a concrete and practical development plan (vs. just a conceptual vision)?

3.0
N/A
3 - An overall plan, major milestones stated.
Feasibility

Is the development plan realistic? Is it based on reasonable goals and timelines?

4.0
N/A
4 - Realistic.
Vision

Is there a larger, long-term vision?

3.0
N/A
3 - A trend with potential.
Dependencies (services or capabilities)

How available, operational, or trusted are the other systems or capabilities on which the project relies?

2.0
N/A
2 - Not fully available or trustworthy.
Current Position

Where is the project now, relative to its vision and plans?

3.0
N/A
3 - Getting there.
Roadmap Score:
3.0

Compliance

There are approximately 3 pages towards the end of the document discussing legal considerations. There is also a separate 15-page document that outlines the terms of use for the platform and token sale, which is fairly comprehensive and professionally written. It is stated that “the Squeezer Framework does not have any legal or partner qualification with the specified cloud providers”. It is stated that SQZR should not be considered security tokens. KYC will be used for the token sale.

Category Breakdown
Token Utility (value through usage)

How much use is there for the token itself (regardless of its value as an investment vehicle)?

2.0
N/A
2 - Minimal or contrived.
Token as Security (tradable instrument)

How valuable is the token as an investment vehicle or financial instrument?

2.0
N/A
2 - Primarily, with few additional rights.
Token/Smart-Contract Readiness

Is the blockchain infrastructure of the project ready for use? Is there a working prototype or MVP? How long until it is operational?

2.0
N/A
2 - Proof of concept or test platform.
Attention to Compliance Issues

How much attention is given to compliance (via token and ecosystem design, token sale participation, etc.)? Is this issue addressed directly and coherently?

4.0
N/A
4 - Specific, detailed.
Legal Review/Risk Assessment

What kind of legal documentation (reviews or agreements) and risk assessment are provided?

4.0
N/A
4 - Professional.
Compliance Score:
2.8

Company and Team

The core team of 7 individuals is listed on the Squeezer website, along with their profile pictures, job titles, and links to LinkedIn profiles. The skill set of the core team is comprised mainly of a background in business development. There are two individuals with a technical background, one of which is the CEO, who has prior blockchain experience as a consultant. The team is not fully developed as there are plans to hire additional developers to build the blockchain cloud connectors in July 2018.

Category Breakdown
Company Stage and Foundation

Is the company already established? Has it raised funds before? Is it mature?

3.0
N/A
3 - Company structure in place.
Background of Lead Team Members

Do we know who they are? Do they have LinkedIn profiles? Do they have solid, relevant backgrounds?

3.0
N/A
3 - Minimally sufficient.
Team Assembly and Commitment

Is a solid, fully committed core team in place? Do they have online (e.g. LinkedIn) profiles showing sufficient relevant experience? Is their participation transparent?

3.0
N/A
3 - Mostly assembled and committed.
Team Skill Set Relevance

Does the amount of talent and skill in each area seem to fit the project requirements?

3.0
N/A
3 - Correlated to project requirements.
Team Skill Set Balance

Is the team well-rounded (biz/tech/blockchain)? Is there sufficient talent and skill in all areas of required development?

3.0
N/A
3 - Somewhat uncertain, probably okay.
Company and Team Score:
3.0

Token Sale

The total number of SQZR tokens is 385 million (40% is for sale, 34% is for the organization, 20% is for the team, 5% is for advisors, and 1% is for the bounty program). Vesting periods are not clearly outlined. The allocation of funds is briefly described (45% is for technical development, 30% is for non-technical staff, 10% is for marketing expenses, 8% is for infrastructure expenses, and 7% is for operating expenses). The soft cap is 7.7 million SQZR and the hard cap is 154 million SQZR, where 1 SQZR = $0.20 USD.

Category Breakdown
Raise Amount Max

Is there a clear cap? Is the maximum raise amount modestly sufficient (as opposed to either greedy or insufficient)?

2.0
N/A
2 - Somewhat greedy or unrelated to plans.
Raise Amount Min

Is the minimum raise reasonable considering the development plan? Are there raise-amount dependent milestones?

2.0
N/A
2 - Only loosely related to plans.
Fund Allocation

Is fund distribution and allocation reasonable and justified?

3.0
N/A
3 - Rough estimates, but sensible.
Token Allocation

Is the ratio of tokens sold to those kept reasonable? Does it prevent the company from having too much control?

3.0
N/A
3 - Sufficient company/community interest balance.
Media Presence and Following

Is the sale being talked about in Reddit, Bitcointalk, Social Media, Medium, etc.? Is information available and accessible? Is there interest?

4.0
N/A
4 - Solid exposure and interest, good impression.
Token Sale Score:
2.8

Use this code to share the ratings on your website